terriblefire wrote: Sun May 26, 2024 7:02 pm
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 ?
terriblefire wrote: Sun May 26, 2024 7:02 pm
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
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Run MuFastROM and then rerun the tests. Working theory is that its only happening when the driver is in ROM.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
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
supaduper wrote: Mon May 27, 2024 1:42 pm
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
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
supaduper wrote: Mon May 27, 2024 1:42 pm
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
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.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Found the issue. I've sent @supaduper and @erique an email with a fw to test.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Seems to be fixed. Want to investigate one more issue before building new firmwares for all the variants of the 123x
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."