exxos's Atari, Amiga & retro forum

terriblefire wrote: 26 May 2024 19:02 Thanks folks. Can you guys try the readdisk.exe with ehide.device as a parameter.. see if you get the lockup

Steve can you alter your readdisk.exe so that it reads and writes data as I take it it only reads data ?

Cheers

supaduper wrote: 26 May 2024 19:13

terriblefire wrote: 26 May 2024 19:02 Thanks folks. Can you guys try the readdisk.exe with ehide.device as a parameter.. see if you get the lockup

Steve can you alter your readdisk.exe so that it reads and writes data as I take it it only reads data ?

Cheers

@erique says he can change it but he has repro'd the issue without writing.

Even just "type >NIL: largefile" will repro the issue. just takes longer.

Writing could corrupt the disk. trying to avoid that

using readdisk largefile I get lockups so I get the same as eric

also for those testing using readdisk if you want to see the output then just go: readdisk ehide.device largefile

Quick experiment to try for those with an MMU.

Run MuFastROM and then rerun the tests. Working theory is that its only happening when the driver is in ROM.

Yep that`ll work, I installed Thomas`s MMUlibs from Aminet and overwrit any old libs that were on my 0S 3.2.2.1 system and actually when installing MMUlibs and it asks what hardware so I selected Phase5 board lol , then make sure you select the MUFastrom option on the install and it will all work :)

I tested by dumping the whole of the WHDload demo`s set , nearly 800mb and it dumped it flawlessly


And now thinking about it all my other 3.1 systems already have FASTROM installed so that`s why it did not show up

MMULibs link below
http://aminet.net/package/util/libs/MMULib.lha

Nice one Steve/Erik

supaduper wrote: 27 May 2024 13:42 Yep that`ll work, I installed Thomas`s MMUlibs from Aminet and overwrit any old libs that were on my 0S 3.2.2.1 system and actually when installing MMUlibs and it asks what hardware so I selected Phase5 board lol , then make sure you select the MUFastrom option on the install and it will all work :)

I tested by dumping the whole of the WHDload demo`s set , nearly 800mb and it dumped it flawlessly


And now thinking about it all my other 3.1 systems already have FASTROM installed so that`s why it did not show up

Nice one Steve/Eric

Contributing factor is that CPU FASTROM is deprecated on 3.2

terriblefire wrote: 27 May 2024 13:51

supaduper wrote: 27 May 2024 13:42 Yep that`ll work, I installed Thomas`s MMUlibs from Aminet and overwrit any old libs that were on my 0S 3.2.2.1 system and actually when installing MMUlibs and it asks what hardware so I selected Phase5 board lol , then make sure you select the MUFastrom option on the install and it will all work :)

I tested by dumping the whole of the WHDload demo`s set , nearly 800mb and it dumped it flawlessly


And now thinking about it all my other 3.1 systems already have FASTROM installed so that`s why it did not show up

Nice one Steve/Eric

Contributing factor is that CPU FASTROM is deprecated on 3.2

So true ! thank heavens for MUfastrom to save the day

supaduper wrote: 27 May 2024 13:55

terriblefire wrote: 27 May 2024 13:51

Contributing factor is that CPU FASTROM is deprecated on 3.2

So true ! thank heavens for MUfastrom to save the day

There is still a bug i need to find. But there is at least a workaround for now.

Found the issue. I've sent @supaduper and @erique an email with a fw to test.

Seems to be fixed. Want to investigate one more issue before building new firmwares for all the variants of the 123x