Quote
Why didn't you attempt to launch ACAtool from the launched WB and see if the IDE speeder is on or off, like I asked? Is the tool crashing, or did this just slip your attention?
My apologies, when you said latter, I assumed you where talking about placing the acatool latter in the startup-sequence. Thus to confirm, if I run the tool after workbench has started, and the tool's removed from the startup-sequence, I can apply PIO mode 4- and activate with no problem or crashes. I do however have to perform a reboot via Ctrl-Amiga-Amiga before sysinfo reports faster read speeds.
Quote
That startup-sequence is full of patches that are of questionable use - FBlit should be removed for sure, and why do you use Cyberpatcher if you don't have an 060?
What's the "maxmem" thing? Why is XSurfIDE even looked for?
Like I said Its a ClassicWB startup sequence (apologies maybe I should have been upfront about the use of the "community pack"). I'm very new to Amiga ownership . I'm learning as I go, I guess you could say I know enough to be dangerous lol. Bloodwych's ClassicWB community pack seemed like the bang for ones buck after much trail and error.
Quote
That startup-sequence is full of patches that are of questionable use
I also questioned if some of these patches may have been messing things up (do keep in mind XSurfIDE and Cyberpatcher are disabled by default, that's why they are raped in if statements, they can be turned off and on by the user and the startup sequence checks to see if they active).
So I did a clean, stock install of workbench 3.9. I used ACAtool to add its self to the startup-sequence with the IDE boost turned on but the system still lock up on a cold boot. Given that this was tested back when I was using the 3.1 kick start, I decided to test again, before posting, with my newly installed 3.x roms.... and would you believe I can boot from a cold boot!
While testing under the clean install I also noticed that I don't need to soft reboot ( Ctrl-Amiga-Amiga) to see the speed boots take affect. I also don't think I ever seen seen the tool remember the IDE Accel. setting.
After all this time it looks like I have an answer. One of the patches in ClassicWB is possibly the root of the problem, or maybe the version of setpatch it uses... also switching to a different kickstart or some combo of all 3? I'll need to do more investigating. Once again Forgive me for not informing you about using ClassicWB at the start. These packs seemed so popular I just assumed most where using them *face palm*. I appreciate you sticking with me and providing support.