modecode for Aranym

[WongCK]

Hi 

Is there a modecode that is available for Aranym via the aranym,sys driver?

The reason I am asking is that I updated my very old Mint 1.19.cur to the latest snapshot from Github and NVDI 4,11 does not work anymore.

It goes to a white screen and seems like the video is not set correction via XaAES video/screendev/modecode as i do not know the proper one to use. I tired the usual 27, 28, 0x801C and even 2 codes from my Falcon (a long shot but I try anything)

The latest snapshot works on my Falcon CT63, with NVDI 4.11 and I had a proper modecode for my Radeon.

Thanks.

rgds

wongck

 

On Tuesday, 16 June 2020, 10:08:30 pm SGT, Thorsten Otto <ad...@tho-otto.de> wrote:

On Samstag, 23. Mai 2020 10:49:12 CEST Jean wrote:

> Hi,

> Sorry not related to aranym but des not know how to reach atari people

> elsewhere; does anyone know what happened to atari-forum? It's been more a

> week it is down.

 

After more than 4 weeks, seems to be back again....

 

--
You received this message because you are subscribed to the Google Groups "ARAnyM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aranym+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/aranym/4458373.CFWM2FIVhz%40earendil.

[Thorsten Otto]

On Freitag, 1. Juli 2022 10:16:15 CEST 'WongCK' via ARAnyM wrote:

> Is there a modecode that is available for Aranym via the aranym,sys driver?

 

No, there isn't. Resolution must be configured in fvdi.sys. Note that if you want to use NVDI together with fVDI, you must disable its screen drivers (by renaming or deleting them). But actually there is not much point in doing so; vector fonts are also provided by fVDI, and NVDI is only needed if you need the printer drivers, are some obscure features that fVDI doesn't support yet.

 

[wong...@yahoo.com]

This was one of my setup for testing the PDF creation tool, so yes, I only need the printing feature.

Just that the new Mint snapshot seems to have broken Aranym with NVDI 4.11 while it is working fine on my Falcon/CT63 with NVDI 4.11.

The old release version of Mint 1,19 works and that was like 7 years old by now, but it is still v1,19. ;-)

I have check all the Mint settings and exactly like on Falcon/CT63. 

Only thing different is the virtual machine and I think it is just not able to switch to correct video mode. 

As on the Aranym, I get mostly white screen and once or twice multiple tiny screens where I can see the desktop... so it is just a mater of video modecode.

Never mind,  I just need to remember not to replace the original Mint 1.19.

[Paul Wratt]

if you can find the fVDI.sys doc, it says how to specify NVDI as the
printer driver (its basically a "fall through" option).

I would suggest maybe a Mint Build from the middle/beginning of 2021
to see if that works, as I was using one from 2020 (with BeePi) that
worked fine. Someone could probably "git bisect" it for you to get an
answer.

Cant you use the 1.19 fvdi.sys "modecode" in the new build?

> --
> You received this message because you are subscribed to the Google Groups
> "ARAnyM" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aranym+un...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/aranym/14627b30-935f-4024-a3bf-c22795b536c5n%40googlegroups.com.
>

[wong...@yahoo.com]

Thanks for responding.

The fvdi,sys does document the NVDI printer fall through within the .sys file it self. Well at least on mine.

I was working together with faucon2001 among others back in 2014 on Atari-forums, early days stuff which later produced the BeePi series.

https://www.atari-forum.com/viewtopic.php?p=246514#p246514 

It's a good read as lots of technical stuff being discussed.

So NVDI 5 does comes up fine with the new snapshot ( but NVDI 5 has issues with non-NVDI printer drivers).

Only anything before NVDI 5 seems does not work on the new snapshot.

And yes, my next step would be try to find something between 2016 (the working 1-19-cur version) and 1-19-be6  (April 2020) as 1-19-be6 the oldest of the newest I have handy on Aranym that breaks with NVDI 4.11. I am not even sure if I have any older version 1-19-xxx kept somewhere on one of my many falcon spare HDD,  just that I have to physically swap HDD each time. Something I try not to do too much on the old IDE ribbon. (other than that it's probably a 68060 build, not meant for Aranym).

Sorry I don't understand this "Cant you use the 1.19 fvdi.sys "modecode" in the new build?"  sentence.

There is no modecode settings for Xaaes on my Aranym , which mean it just takes the default screen rez. 

So there was no clue as to what to use. 

[Miro Kropáček]

Oops, sorry, replied privately instead of mailing list.

Well, Pep's change to mode code is quite recent, can you try:

- https://tho-otto.de/snapshots/freemint/bootable/freemint-1-19-a8c0429f-040-aranym.zip (this is a build before my fix of Pep's commit, maybe I'd messed up something there)

- https://tho-otto.de/snapshots/freemint/bootable/freemint-1-19-2b8d5dbc-040-aranym.zip (this is before Pep's work on mode codes)

On Tue, 5 Jul 2022 at 07:29, WongCK <wong...@yahoo.com> wrote:

Yes, that's the one I am talking about.

I always left it blank (i.e. no video=xx, no screendev=xx and no modecode=xx) and it was working for NVDI 5 on the latest snapshot (downloaded end Jun 2022).

However just swapping NVDI 4.11 for NVDI 5, will boot a white screen.

Funny thing is that I had the 1-19-cur install ( timestamp as 2014 on the file system) and that works with NVDI 4,11.

On the real Atari - Falcon CT63 with CTPCI Radeon, the latest snapshot works with NVDI 4.11 and the only difference is that I am telling Xaaes to use the modecode for my Radeon. So I figure that for the Aranym case, it looks like it is not switching to correct screen modecode, and therefore the question.

On Friday, 1 July 2022 at 06:07:28 pm SGT, Miro Kropáček <miro.k...@gmail.com> wrote:

On Fri, 1 Jul 2022 at 10:18, 'WongCK' via ARAnyM <ara...@googlegroups.com> wrote:

It goes to a white screen and seems like the video is not set correction via XaAES video/screendev/modecode as i do not know the proper one to use. I tired the usual 27, 28, 0x801C and even 2 codes from my Falcon (a long shot but I try anything)

You shouldn't be setting anything there, let the system use the current resolution. I hope I understood you correctly that we are talking about this mode code: https://github.com/freemint/freemint/blob/master/xaaes/src.km/example.cnf#L158

--

http://mikro.atari.org

--

http://mikro.atari.org

[WongCK]

Hi Mikro,

As usual....  THANKS !! 

The version MINT-2b8 works with NVDI 4.11 while the MINT-a8c gave the white screen.

You can see the results below from bash.

--
You received this message because you are subscribed to a topic in the Google Groups "ARAnyM" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/aranym/iyeFnaoSMeU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to aranym+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/aranym/CAN5rfbQA-eC-nARFeYNu2c0BauZ64C11e3ys6fWvvDg2k0zVwA%40mail.gmail.com.

[Miro Kropáček]

On Sun, 10 Jul 2022 at 07:47, 'WongCK' via ARAnyM <ara...@googlegroups.com> wrote:

As usual....  THANKS !! 

No need to thank me for finding a bugged build. ;-)

 

The version MINT-2b8 works with NVDI 4.11 while the MINT-a8c gave the white screen.

Can you describe me your setup? I.e. whether you are bootstrapping freemint from hostfs or booting from a disk image, EmuTOS/TOS version, what apps are in AUTO and what do you execute from mint.cnf?

--

http://mikro.atari.org

[WongCK]

I am using disk image, 

I did not use any of the emutos nor fvdi from the package. 

I just copied the system folder, move MINT.PRG ( & rename it) to AUTO. Copied my own MINT.CNF & XAAES.CNF. Change the xaloader path. 

Emutos is v1.1.1.

It then run Xboot where I select the configuration.

For this running configuration -

AUTO

1. Xboot

2. Mint_2b8.prg (yes I renamed it so that I know which one to select)

3. NVDI 4.11

4. Zmagxsnd

5. Clocky

My Mint.CNF is the same for all configuration, except I update INIT to run the new Xaloader.

My Xaaes is also the same for all configuration so that it runs the same teradesk, toswin, etc

fsck on my ef2fs is run from MINT.CNF file.

Fvdi.prg is run from within MINT.CNF file after fsck.

Also in MINT.CNF and runs after fvdi are tzinit, network stuff and then INIT (all in this order).

Fvdi.prg is v0.96beta3Lgcc-FT2  if that makes sense. I cannot remember where I got it from. should be somewhat new I guess.

All pseudo cookie are disable ( so only real NVDI 4.11 cookie is placed by NVDI)

nvdifix  xbiosfix and booted are uncommented.

rgds

wongck

--

You received this message because you are subscribed to a topic in the Google Groups "ARAnyM" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/aranym/iyeFnaoSMeU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to aranym+un...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/aranym/CAN5rfbQyUS0U8egxvZw%2BJM%3DdHtNnPOXOvWp3e_v6%3DrF1i0F%2BvA%40mail.gmail.com

.

[Miro Kropáček]

On Sun, 10 Jul 2022 at 14:51, WongCK <wong...@yahoo.com> wrote:

I did not use any of the emutos nor fvdi from the package. 

If you find some time, could you use those from the package please?

 

AUTO

1. Xboot

2. Mint_2b8.prg (yes I renamed it so that I know which one to select)

3. NVDI 4.11

Are you sure about 2. and 3. ? If I boot with NVDI first, I get white screen on both 7f0 and 2b8.

... and if I boot NVDI before MINT.PRG, it works fine on both 7f0 and 2b8.

nvdifix  xbiosfix and booted are uncommented.

Same for me.

--

http://mikro.atari.org

[WongCK]

yes, I plan to use the programs from the package and also replace the binaries for /bin as well from the package.

here is my AUTO folder unsorted. All NVDI are after Mint.

--

You received this message because you are subscribed to a topic in the Google Groups "ARAnyM" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/aranym/iyeFnaoSMeU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to aranym+un...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/aranym/CAN5rfbT1rfEn6eqDbCPYA4bGc%2B5Y10det8iqzQzV1wYUrX_Tow%40mail.gmail.com

.

[Miro Kropáček]

On Sun, 10 Jul 2022 at 16:24, WongCK <wong...@yahoo.com> wrote:

yes, I plan to use the programs from the package and also replace the binaries for /bin as well from the package.

here is my AUTO folder unsorted. All NVDI are after Mint.

Interesting. I have the exact same binary (NVDI 4.11d) and I absolutely can't reproduce your use case. I even tried the EmuTOS from git. No change -- if putting NVDI.PRG before MINT.PRG, it works on all builds, if after -- doesn't work on any.

So if you manage to reproduce this in a more isolated environment, I'll be glad to take a look but right now, there doesn't seem to be a way to reproduce it.

--

http://mikro.atari.org

[wong...@yahoo.com]

I just tried the emutos and fvdi from the package, even changed the fvdi.sys uncommented singlebend like in the package.

same white screen on a8c but 2b8 continue to work.

The package emuTos is v1.0 while I was using v1.1, anyway no difference in NVDI behaviour.

here is my AUTO folder unsorted. All NVDI are after Mint.

Interesting. I have the exact same binary (NVDI 4.11d) and I absolutely can't reproduce your use case. I even tried the EmuTOS from git. No change -- if putting NVDI.PRG before MINT.PRG, it works on all builds, if after -- doesn't work on any.

I will try NVDI ahead of Mint, but I remembered that placing it after Mint was preferred for printing reasons.

 

So if you manage to reproduce this in a more isolated environment, I'll be glad to take a look but right now, there doesn't seem to be a way to reproduce it.

 

it's ok, at least 2b8 seems to work and that's pretty new build with lots of improvements.

[Miro Kropáček]

On Sun, 10 Jul 2022 at 16:53, 'wong...@yahoo.com' via ARAnyM <ara...@googlegroups.com> wrote:

I just tried the emutos and fvdi from the package, even changed the fvdi.sys uncommented singlebend like in the package.

same white screen on a8c but 2b8 continue to work.

The package emuTos is v1.0 while I was using v1.1, anyway no difference in NVDI behaviour.

Hmm, if your image doesn't contain sensitive data, feel free to upload it somewhere so I can take a look. It's really puzzling. 

Maybe it is an Aranym issue after all, I'm running latest git version here on Linux.

--

http://mikro.atari.org

[wong...@yahoo.com]

If I move NVDI to ahead of Mint-a8c, Mint will successfully boot up to the desktop.

However, both 2b8 and a8c exhibit following

1. PS does not show NVDI any more.

2. When I select the printer.cpx, FVDI complained  about not handling vq_devinfo.

3. Only system fonts available. 

So I need the NVDI to be after MInt for printing... this is my test environment. 

I do not want to mess up Falcon so I created this testing env on Aranym.

[wong...@yahoo.com]

I am on windoze 10.

[Eero Tamminen]

Hi,

On 10.7.2022 15.51, 'WongCK' via ARAnyM wrote:
> I am using disk image, I did not use any of the emutos nor fvdi from the package. I just copied the system folder, move MINT.PRG ( & rename it) to AUTO. Copied my own MINT.CNF & XAAES.CNF. Change the xaloader path.
> Emutos is v1.1.1.

EmuTOS had a MiNT MP / VDI bug which was fixed after v1.1.1:
https://github.com/emutos/emutos/commit/b245f3cfac7bdb146401a642bbf49ed4de1283cd

Please try a recent EmuTOS snapshot instead.


- Eero

> It then run Xboot where I select the configuration.For this running configuration -

> AUTO1. Xboot2. Mint_2b8.prg (yes I renamed it so that I know which one to select)3. NVDI 4.114. Zmagxsnd5. Clocky
> My Mint.CNF is the same for all configuration, except I update INIT to run the new Xaloader.My Xaaes is also the same for all configuration so that it runs the same teradesk, toswin, etc
> fsck on my ef2fs is run from MINT.CNF file.Fvdi.prg is run from within MINT.CNF file after fsck.Also in MINT.CNF and runs after fvdi are tzinit, network stuff and then INIT (all in this order).
> Fvdi.prg is v0.96beta3Lgcc-FT2  if that makes sense. I cannot remember where I got it from. should be somewhat new I guess.All pseudo cookie are disable ( so only real NVDI 4.11 cookie is placed by NVDI)nvdifix  xbiosfix and booted are uncommented.

[Miro Kropáček]

On Sun, 10 Jul 2022 at 22:37, Eero Tamminen <o...@helsinkinet.fi> wrote:

EmuTOS had a MiNT MP / VDI bug which was fixed after v1.1.1:
https://github.com/emutos/emutos/commit/b245f3cfac7bdb146401a642bbf49ed4de1283cd

Please try a recent EmuTOS snapshot instead.

This wouldn't and wont help because the issue is linked with usage of (Emu)TOS VDI, not its replacements (which actually do the right thing).

The issue has been way more subtle: https://github.com/freemint/freemint/pull/269

Thank you Wongck for reporting and testing, you have uncovered a pretty serious bug in XaAES. 

--

http://mikro.atari.org

[wong...@yahoo.com]

Thank you Wongck for reporting and testing, you have uncovered a pretty serious bug in XaAES. 

 

You are welcome. Thanks to you and the Mint team for continuing support on Mint. This make my Falcon more fun to use!!