It now works but why?

[Cosmic Puppet]

So there's a selection here:

20200830_203355.jpg

Which gives you these options:

20200830_203401.jpg

No matter what I select Notator crashes when being used with EmuTOS. (Just Notator with NVDI 2.51 is fine)

But if I double click on this:

20200830_202954.jpg

I get this "aquire VDI -memory" that's unclickable:

20200830_203013.jpg

If I click "Read" and then go into the AUTO folder:

20200830_203021.jpg

and choose NVDI.PRG:

20200830_203026.jpg

I'm able to select "aquire VDI -memory" and save:

20200830_203033.jpg

This will then let Notator load.

I tried lots of combinations. I can leave all boxes unchecked, but if I uncheck "aquire VDI -memory" I get this:

20200830_194035.jpg

This is unchecked by default and only accessible through this folder.

Also, one time I tried to access this folder I got this:

20200830_193809.jpg

(It's very pleasing to look at but I'm guessing it's some weird memory thing)

After losing my whole day to this, as I hadn't remembered this was what was doing the making and breaking, can anyone tell why this is the case?

I have no idea what's going on. I've just fixed it by a process of elimination and taken my sanity with it! :shock:

[exxos]

Isn't that relating to when graphics cards are used ?

[Cosmic Puppet]

Isn't that relating to when graphics cards are used ?

All I know is that without it Notator crashes with EmuTOS.

Tick the box and everything is hunkydory.

[Cosmic Puppet]

20200830_213827.jpg

I don't understand what this means, it says to leave it unchecked, yet checking this box makes Notator load with EmuTOS.
Unchecking it causes a crash.

[exxos]

does it do the same with 104 or 206 ?

[Cosmic Puppet]

does it do the same with 104 or 206 ?

Notator loads fine when used with just NVDI 2.51 (also doesn't freeze in the editor) This is TOS 1.04
When I add EmuTOS Notator then crashes before loading unless I select the enquire VDI -memory.

Curiously I was just getting 2 bombs on start up but still being able to load Notator with this box checked so I changed the load order putting EmuTOS before NVDI and the bombs have stopped.

I don't have TOS 2.06

[exxos]

Curiously I was just getting 2 bombs on start up but still being able to load Notator with this box checked so I changed the load order putting EmuTOS before NVDI and the bombs have stopped.

Ah so your running the PRG of EMUTOS ? In that case yeah you need to load the OS (EMUTOS) before loading up anything else..

I assume EMUTOS being loaded into RAM might also cause issues.. You really need to try a proper EMUTOS ROM and see if the same oddness happens.

[Cosmic Puppet]

Curiously I was just getting 2 bombs on start up but still being able to load Notator with this box checked so I changed the load order putting EmuTOS before NVDI and the bombs have stopped.

Ah so your running the PRG of EMUTOS ? In that case yeah you need to load the OS (EMUTOS) before loading up anything else..

I assume EMUTOS being loaded into RAM might also cause issues.. You really need to try a proper EMUTOS ROM and see if the same oddness happens.

Thanks @exxos I wasn't even aware that it had to come first all though I usually have it first as things show up twice on start up if I don't.

I'm carefully adding things. EmuTOS, NVDI 2.51 and Notator are all getting along now. If you mean there's a physical Chip with EmuTOS on it, I need to have TOS 1.04 too for games, which is how the other SD card is setup.

[thorsten.otto]

I don't understand what this means, it says to leave it unchecked, yet checking this box makes Notator load with EmuTOS.
Unchecking it causes a crash.

Normally that sounds more a problem of one of your accessories rather than notator.

The reason behind this is: VDI allocates some memory during v_opnvwk(). That is a GEMDOS call. But accessories aren't GEMDOS processes, they are managed by the AES, and the memory that VDI allocates is therefor assigned to either the desktop or the application that is currently running (notator in your case). Whenever you start or stop a application, the current application will be terminated, and that will free the memory that VDI allocated, but the VDI is not notified about this fact.

Conclusion: you should check the accessories you are using (firstly be deactivating all of them). I would bet one of them is causing the trouble.

[Cosmic Puppet]

I don't understand what this means, it says to leave it unchecked, yet checking this box makes Notator load with EmuTOS.
Unchecking it causes a crash.

Normally that sounds more a problem of one of your accessories rather than notator.

The reason behind this is: VDI allocates some memory during v_opnvwk(). That is a GEMDOS call. But accessories aren't GEMDOS processes, they are managed by the AES, and the memory that VDI allocates is therefor assigned to either the desktop or the application that is currently running (notator in your case). Whenever you start or stop a application, the current application will be terminated, and that will free the memory that VDI allocated, but the VDI is not notified about this fact.

Conclusion: you should check the accessories you are using (firstly be deactivating all of them). I would bet one of them is causing the trouble.

Hi @thorsten.otto That's what I've been up to today. Getting NVDI 2.51 to work with Notator and then getting EmuTOS to run with them. Spent all day on this and have started adding back accessories 1 by 1. All back and working brilliantly. The only thing left out now is Deskpic which causes Notator to freeze in the note editor when keys D, W and H are pressed.

Finding this freeze has been very useful in testing the stability of Notator.

I've found though that NVDI 2.51 is best last in the boot order, otherwise Notator crashes upon loading with this:

20200830_194035.jpg