did boing bags 2 rom update. Now I get alert when booting...

  • Thread starter Thread starter Mendel
  • Start date Start date
  • Replies Replies 33
  • Views Views 12902
I installed os3.9 +bb1 and bb2 + classic workbench on my pc (winaue), put the working 3.1 libs for my 1260 in os3.9 libs:, packed all with lha and transfered the .lha file on my real amiga hd. Restore the .lha on my boot partition.
When I boot the amiga, I have the same failure as described in this thread.

I read about a power up in this thread. Does I have to do something with this power up disc, even if I manually copyed the 68040 and 68060 to libs: ??

or do I have to start to modify my startup sequence as described in this thread, if yes, which modification to start with ?
Thank in advance.

I forgot : My real amiga HD boot partition is formated with pfs3ds, the last aminet version. I do not know if it makes a difference....

This installation is working under winaue.
 
Last edited:
We certainly need some more info in order to help more.
1. What is the capacity of your hard drive?
2. How large is your system partition?
3. Under WinUAE if you issue "version scsi.device" under a CLI what do you get?
4. What are the versions of 68040.library and 68060.library that you put ?
 
My hard drive is 8GB (CF)
System partition 1,6 gb
I do not have access to a pc now to check the scsi version.
The 68040 and 68060 are the working one from my 3.1 system. Is there special version for os3.9?

I just got the system to boot in 3.9

I just put a ; before all related scsi.device things in the startup sequence and put a line with "C:SetPatch SKIPROMMODULES "scsi.device" QUIET"

I saw a post from you in another where you was giving this advice to someone. I tried it ant it works.

It is the first time I boot in Classic workbench 3.9 , Its running slowly in comparaison to 3.1...
It uses cybergraphx in screen mod, is it normal ?
 
I'd play safe and put a system partition of 950MB (it's more than enough for EVERY system and possibly program that you'll ever put).
If your 040/060 libs work ok for your 3.1 system I guess they are ok as well for 3.9.
Since the SetPatch line that you put, works... it means that you're getting some issues with the SCSI.device and PFS3.

OS3.9 is definitely slower than WB3.1 (that's why it requires AT LEAST an 020 and 4MB RAM) while 3.1 runs even with 512KB chip and an 68000 CPU.
You can make it more quick by removing some stuff like AmiDock, ASyncWB, RawWBInfo etc.

To be able to run just fine, I'd strongly suggest to either load a SCSI.device that is compatible with PFS3.
For example under ClassicWB's System partition head to drawer MyFiles/LargeHD/128GB_Support
There you find a number of SCSI.devices which you can rename to scsi.device and copy to Devs. (There's a script in startup-serquece that IF it finds a scsi.device in Devs it loads it via LoadModule).
For example SCSI_v43_47 by Cosmos has inside a latest version of PFS which you can copy to L: and assign to RDB instead of yours. You can also use this scsi.device and report back.

Personally I use Doobrey's 44.2 scsi.device with SFS filesystem and never failed me.
 
Wow I just did a clean cwb install on a 32GB CF card and almost gave up as it wasn´t booting but then I started to retrace my steps that I took last time.

I had to do both edit the startup sequence and install the 060 drivers to make it boot :D I have a booting 32GB CF card through fast ata!

mfilos and johnim, thanks you both!
 
@mfilos

Thanks very much.
It works now with cosmos scsi.device version 43.47
 
Last edited:
Nice to know u got it working mate :)

Cosmos scsi.device works very nice with PFS3 and it's 20% faster than the stock 3.1 scsi.device. It doesn't run well on partitions over 4GB assigned as SFS though.
For SFS best scsi.device imho is 44.2 of Doobrey
 
For me, on my config (8GB cf flash with ide to flash adaptor), sysinfo showed me with the scsi from 3.1 + SpeedyIDE about 1,74 mb/s, and the cosmos new one + SpeedyIDE give me about 1,79. It is about 8% more.
 
Do you mean a fastata mkx ?
Will this really boost the workbench reactivity (open windows, start app,...) ?
 
Last edited:
No i mean that accelerators in general, speed up also the disk access :)
FastATA or Idefix Express also speed up the disk access.
You can see some slight difference in Workbench, but don't expect miracles.
For best responsive workench (without RTG) the best way to speed up your system (windows/icons loading) is to either reduce the screen resolution or your color depth :)
 
For me, fastata with cf card gives only about double the speed from standard ide, which is not nearly enough for my needs so I will go for something other than CF cards next.
 
It all depends on the PIO Mode that you set on ATA3Prefs program.
If u manage to make your CF/HD work in PIO4 or even PIO5 you'd be surprised on the speed increase.
It's just that FastATA tends to be kinda picky on the Hard drives and in many circumstances you won't be experiencing more than PIO3 mode.
 
Indeed, if I put anything more than PIO3, I start getting block read errors. I think PIO 3 should still allow for more than 10MB/s.
 
You must log in or register to reply here.
Back
Top Bottom