Can OS3.9 patches run fully on an A4000D?

[matthey]

I got a WarpEngine with BB2 installed by I skip the exec library update which is slower and reported as buggy sometimes or certain situations. I've planned to give it a try on Piru's excellent exec.library replacement but till today I never bothered...

The AmigaOS 3.9 BB2 exec.library is faster in general than earlier. Memory pools and CopyMem()/CopyMemQuick() are faster for example. Several bugs have been fixed and it seems very stable here. The only thing slow and buggy about it that I know of is the BoingBag update/double reboot process.

[Vanilla]

Have you tried an IDE hard drive?

No I haven't. I have a CDRW on my IDE port. Could be a good idea to test.

[Vanilla]

I have no experience with the Warp Engine but most accelerators can use other CPU libraries. There are exceptions though. I use the Mu/Thor/mmu.library cpu libraries with my Phase5 accelerator. Read the docs well though.

I gave the MMU 68040 library a test, but it ends up the same, machien can't boot. Having said that, I found a 68040 library on the OS3.9 CD, which is different to all I have! So I'm going to give that a shot. :-)

II replaced the latest FFS in my RDB and L: without problems. I use the smartfilesystem now with my CSMK3 ultraSCSI. I don't know what to tell you about putting the latest FFS in the RDB after having problems except back everything up if you are going to try it.

Well I checked and I have these versions. Don't know if there is a conflict there. I'm rather stuck on FFS as being in the RDB it crashes as soon as the machine boots and so before any patches are loaded. Don't know wbay way around that, unless I have a known buggy version.

Fast-File-System: 45.13
SetPatch: 44.38

I wonder what other system files can conflict with buggy versions I should check?

[Vanilla]

I got a WarpEngine with BB2 installed by I skip the exec library update which is slower and reported as buggy sometimes or certain situations. I've planned to give it a try on Piru's excellent exec.library replacement but till today I never bothered...

Damn it my post was wiped out!  It logged me out during replying and I lost everything! Have to start again :-O

How did you go?

Anway, as someone said above if it was botting and the hardware config is the same it should be software. But from my experience with the A4000D a lot of stuff can have bad contacts. Sometimes I just have to push the CPU card a bit further after I moved the machine around, to make it work again.

I've been having trouble with my hardware. The A4000 was crashing on power up. I tried pushing in the CPU card and it seemed to help. But I'd done the same thing earlier and the crashing came back. Once I got it going my keyboard went dead and the caps lock started flashing. That worried me, as the last time I saw that, was when my A500 started randomly resetting and the keyboard was killed by a faulty power supply.

Just then I got it to boot but the screen was black or out of range! It was my PicassoI\V card shorting on the motherboard RAM. I can't believe these were sold as an expensive professional device if something as obvious as a short can trip it up. Were these sold with plastic protectors underneath? I am going to need one!

The termination on the WarpEngine is also a pain. Have you changed any external device ? My chain is terminated by the external CDRom, I have to keep it on otherwise it won't boot. I tried once to get an external terminator (can't remember which) and it didn't work at all! And this was a terminator fot SCSI2.

I don't have any external devices. I have a CDRW on the internal IDE and a my HD is on the WarpEngine SCSI bus as a single device. I set up all the SCSI jumpers and without OS3,9 patches messing my system up it usually boots fine.

But, I have progressed a little further somewhat here. I installed the OS3.9 68040.library and then tested the full SetPatch. I was able to get to the early boot screen! What's more, I could even boot off floppy! I rebooted and it was able to reset and reboot off the floppy. :-D

But, off the HD it still got stuck. Even just trying to boot into a shell stumped it. And me. ;-)  I am wondering if the RDB is causing this. Currently no FFS is installed in there as I don't want to plug in an old one but the new one crashes! Will test one one though. But the FFS I am using must be corrupt. Hmmm, think I should do a virus test. That would do some wreckage!

[matthey]

@Vanilla

There is a FastFileSystem patch from 45.13 to 45.15 in the Amikit link I posted...

http://amikit.amiga.sk/patches.htm

Setpatch 44.38 is what I use and is as far as I know the newest.

Thomas Richters mu 68040.library requires extra steps to set up. You can't just copy the 68040.library to Libs:. 680x0.library and mmu.library are required in Libs: also. MMU-Configuration may be needed and require editing on some setups in ENVARC:. It's best to read the docs and use the install. It's probably possible to get this working if you got the latest C= 68040.library working. The latest C= version is probably fine if it's working well. It's better to use a newer 68040.library as the FPU support was updated and a FPU resource installed that speeds up the newer FPU math libraries.

[F0LLETT]

@Vanilla

There is a FastFileSystem patch from 45.13 to 45.15 in the Amikit link I posted...

http://amikit.amiga.sk/patches.htm

Setpatch 44.38 is what I use and is as far as I know the newest.

Thomas Richters mu 68040.library requires extra steps to set up. You can't just copy the 68040.library to Libs:. 680x0.library and mmu.library are required in Libs: also. MMU-Configuration may be needed and require editing on some setups in ENVARC:. It's best to read the docs and use the install. It's probably possible to get this working if you got the latest C= 68040.library working. The latest C= version is probably fine if it's working well. It's better to use a newer 68040.library as the FPU support was updated and a FPU resource installed that speeds up the newer FPU math libraries.

Does the Amikit 45.15 FFS patch include toni's (WinUAE) 45.14p patch? which lets you use drives over 128GB on a real Amiga?

[matthey]

@F0LLETT

It doesn't look like it. It patches the AmigaOS 3.9 BB2 FastFileSystem. Where can Toni's patch be found?

[F0LLETT]

@F0LLETT

It doesn't look like it. It patches the AmigaOS 3.9 BB2 FastFileSystem. Where can Toni's patch be found?

On Aminet.

Also, Doobrey from EAB, just posted about a patch, he has done for the 39 BB2 scsi.device that includes plandon and toni's patches for the scsi.device.
He also removed some debug stuff that increases the speed.

[Crumb]

@thomas

isn't possible to update the "Rom update" file so the user just has to update the scsi.device, ram-handler, fastfilesystem... inside that file? It would be more comfortable and "cleaner" for the user...

[matthey]

@F0LLETT
Thanks.

I didn't find Doobrey's patch on his web site. Did he upload to Aminet and I missed it or is it not yet available?

[F0LLETT]

@F0LLETT
Thanks.

I didn't find Doobrey's patch on his web site. Did he upload to Aminet and I missed it or is it not yet available?

I didnt say his site, I said EAB (English Amiga Board).

[HammerD]

Well for example all the files in the BB2 RomUpdate and then there are some further patches that you can download from AmiKit's webpage.

[matthey]

I didnt say his site, I said EAB (English Amiga Board).

Thanks again.

Looks like the IDE version of scsi.device for now. Here's the link to the thread (for others)...

http://eab.abime.net/showthread.php?p=572209

[Vanilla]

Thanks matthey. Will test and reply back.

[F0LLETT]

Thanks again.

Looks like the IDE version of scsi.device for now. Here's the link to the thread (for others)...

http://eab.abime.net/showthread.php?p=572209

I stuffed this on the deneb and it said for IDE access 44.2 but for HDToolbox, it kept giving me older version so need the scsi version now, .

[number6]

Hello all.

I have been with the help of a friend been putting together a nice A4000D with a WarpEngine and 68040 @ 40Mhz. I now have 128MB of 60ns RAM on my WarpEngine as well. So I have disabled the wait state and it all seems stable. Plus a nice PicassoIV to boot! :-)

I have a 9GB SCSI HD on the WarpEngine's SCSI bus, but put a CDRW on the A4000 IDE bus. My plan was to use the OS3.9 scsi.device with the CDRW to avoid any IDE fix software, a plan that worked well on my A1200D. But so far the A4000 refuses to budge and OS3.9 won't let me do this!

My friend told I need both Boing bags installed for a fully working system. So this is what I tried to do. But, I found I always have to disable the ROM patch, as the machine cannot boot afterwards. :-?

I've got the WarpEngine 68040.library in there and both BoingBags installed. I made sure the OS3.9 patch files are in there and activated in start up. But to no go.

It always ends up the same. The patch installs, reboot ands the machine just sits there with the floppy drive clicking. As if it if started booting and then lost the drive. The HD light flashes briefly before this happens. I can put in a floppy but it just reads it and stops.

Now it looks like the early startup screen is still "there" as when I hold down the mouse buttons after a reset the LED flickers. Like it does when it comes up. But there is only a blank display. Nothing on my PicassoIV VGA out nor the RGB. And without key shortcuts I can do nothing.

I tried to set echo on in the start up script but that was useless as it never gets to execute  it after the first SetPatch installs and reboots! I'm really lost here. I've spend months trying to figure this out but it seems no one is around who has ever fully installed OS3.9BB1+2 on an A4000 with a WarpEngine! :-?

Like many others, I had updated at one time.
Then I elected to do a fresh install of OS3.9 (CD), filenote the lot, and install BB1 and BB2, just to see what would happen.
No issues. WarpEngine 68040 @ 40Mhz with last HD on chain terminated. CDRW/DVD added to IDE, due to lack of supply of SCSI CDRW replacements.

Maybe someone else can be more specific about the install advisement on using the old ROM file in the cases where the newer ROM file fails. I don't think I ever quite learned anything about the true difference between the 2 and why some machines successfully can use the new file whilst others can not.

#6