Classic WB 3.9 and PPC + Bvision problem?

27 January 2012, 17:02

I have a problem with the Classic WB 3.9 pack.
My system is a A1200 with Blizzard PPC 060@50 and 330mhz, I also have a Bvision and 128megs of RAM.

When I do a regular clean install of WB 3.9 and the 060/PPC libs on my 8gig CF card on Winuae, and the puts it back on my amiga, everything works just fine. But when I try to do the same with classic WB 3.9 pack, the HDD lamp flashes for one second and the the powerlamp starts to blink and the computer resets and repets this cycle forever.

My question now is, do I need some special LIB or driver if I have a PPC card and wanna use this wonderful WB pack? Maybe some of you guys have a PPC card and have experience the same thing?

The Fblitter and Copper is off.

Regards

Bloodwych · 27 January 2012, 17:19

I don't have definite answer myself - all I can suggest is disabling more of the components under the Settings menu (eg cyberBugFix, magic menu, tools daemon etc) to try and get it back to as close as a default install as possible then install your drivers and re-enable one at a time.

However it sounds more like a setpatch issue if it's doing it from the off - check that the setpatch options are correct for your hardware in the startup-sequence file. By default, it loads the scsi.device driver for large hard drive support. Your hardware may need a different driver than the standard BB2 one in the ClassicWB.

Hopefully someone with similar hardware can help you out. I only work in WinUAE and on a standard A1200 with fastram.

ancalimon · 27 January 2012, 18:46

Here's what I remember:

You need to have the latest powerpc.library (Warpup) and the latest ppc.library (emulated version). You need Warp3d and the latest CyberGraphx4 (with patches)

You need to have blizkick with the necessary module to remove ppc.library from ROM.

You also need something called bppcfix

In my opinion: Don't use loadmodule stuff. Don't use hacks like fblit, ftext, etc...

The only hack I used was MCP with some of its options turned off.

mfilos · 27 January 2012, 19:22

I have used just fine ClassicWB 3.9:
- On my A1200's BPPC/BVision combo (CGX4)
- On my A4000's CSPPC/PicassoIV combo (P96)
- On my A4000's CSPPC/CVisionPPC combo (CGX4)
- On my A4000's CSPPC/Grex/Voodoo2 combo (CGX4)
...without a single issue!

Be sure to disable Fblit/Ftext, BlazeWCP, IconsBeFast, CyberBugFix.
Also be sure to use the latest 060 libs for your card and you'll be fine.

27 January 2012, 20:11

Thanks for you answers!
I belive Bloodwychis right, I changed the Scisi.device to latest update from cosmos and now the HDD lamp starts to blink, after one second there is a reboot and then the HDD lamp lights (not blink) and nothing happens.
It works perfect in Winuae thou...

I will try to install this on a 4gig CF card. Maybe it´s just sensitive with big CF cards?

mfilos · 27 January 2012, 20:55

Some versions of Cosmos SCSI.device along with Doobrey's AFAIK have some issues with PFS3?
What filesystem are you using in your A1200's HD mate?

I'd suggest to use SFS to be sure.

05 February 2012, 00:34

This is strange! I got it working with a sandisk 4GB card

BUT when I try the 8GIG sandisk card with patched scisi.device the HDD CF card locks, and it just lights and stays lighten.

When I swap back to ClassicWBADV 3.1 and a Blizzard 1260 on the same card everythings works just fine

I cant figure out why it wont work with the 8gig card when i go for WB3.9?

I use SFS

mfilos · 05 February 2012, 02:38

Open a CLI under the 3.9 version and issue "version scsi.device" and tell us what is showing

05 February 2012, 16:53

Thanks for the support

I belive this could be solved pretty easy???

The version number is scsi.device 43.43

mfilos · 05 February 2012, 20:26

Ok... this version is the scsi.device version that exists inside the file "AmigaOS ROM Update" under Devs that came with the BB2 update.
Since a new scsi.device is loaded upon boot, you MUST remove/rename the scsi.device from Devs: since Bloodwych's Startup-Sequence searches for a scsi.device in Devs: and if it founds it, it tries to load it with LoadModule command!

I guess that's a reason why the boot is having issues.

If that doesn't work, just make the following trick to see what else there is to check.
Edit Startup-Sequence and command the SetPatch line by putting a semicolon in front of it (

and then press enter and instead write the following command:

Code:

C:SetPatch NOROMUPDATE QUIET

This command will bypass the BB2 update so no new scsi.device will load (alas Bloodwych's script will try and load his own scsi.device.

Report back with the findings

05 February 2012, 23:41

YES!!! Thanks!
C:SetPatch NOROMUPDATE QUIET, did it

Thank you Mfilos for your support, now I can fill my HDD with some more cool PPC stuff

And thank you Bloodwych for this wonderful WB

Quote:

Originally Posted by mfilos

Ok... this version is the scsi.device version that exists inside the file "AmigaOS ROM Update" under Devs that came with the BB2 update.
Since a new scsi.device is loaded upon boot, you MUST remove/rename the scsi.device from Devs: since Bloodwych's Startup-Sequence searches for a scsi.device in Devs: and if it founds it, it tries to load it with LoadModule command!

I guess that's a reason why the boot is having issues.

If that doesn't work, just make the following trick to see what else there is to check.
Edit Startup-Sequence and command the SetPatch line by putting a semicolon in front of it (

and then press enter and instead write the following command:

Code:

C:SetPatch NOROMUPDATE QUIET

This command will bypass the BB2 update so no new scsi.device will load (alas Bloodwych's script will try and load his own scsi.device.

Report back with the findings

mfilos · 06 February 2012, 20:56

OK i'm glad it works with this.
By issuing the NOROMUPDATE option in SetPatch declaration you're not using the BB2 update to the BB2 version's ROM Modules:
- bootmenu
- console.device
- exec.library
- filesystem.resource
- filesystem
- ram-handler
- scsi.device
- shell

They might not be important to you but some are nice to have.
I'd suggest try the following SetPatch declaration instead (for testing it)

Code:

C:SetPatch SKIPROMMODULES scsi.device QUIET

That will load all the BB2 updated ROM modules EXCEPT the scsi.device which will remain the default (or the one that gets updated by the LoadModule declaration).

If your Amiga boots just fine with this, then you're set for sure

ancalimon · 06 February 2012, 22:51

You should use blizkick instead of setpatch to load at least some of those updates.

08 February 2012, 18:53

Thanks! This line is working aswell

@ancalimon why is blizkick better?

Quote:

Originally Posted by mfilos

OK i'm glad it works with this.
By issuing the NOROMUPDATE option in SetPatch declaration you're not using the BB2 update to the BB2 version's ROM Modules:
- bootmenu
- console.device
- exec.library
- filesystem.resource
- filesystem
- ram-handler
- scsi.device
- shell

They might not be important to you but some are nice to have.
I'd suggest try the following SetPatch declaration instead (for testing it)

Code:

C:SetPatch SKIPROMMODULES scsi.device QUIET

That will load all the BB2 updated ROM modules EXCEPT the scsi.device which will remain the default (or the one that gets updated by the LoadModule declaration).

If your Amiga boots just fine with this, then you're set for sure

mfilos · 08 February 2012, 19:59

I guess you're now set mate! Nice

Blizkick is just an nice application that just loads modules into Blizzard's flash memory. You can use it as you were making some custom ROM.
Although... since it requires a reboot to load the appropriate modules into it's flash... I don't see any actual reason of using it instead of the LoadModule command.
Sure it's faster and more hardcore... but dunno

It's a nice feature for all Blizzard accelerators but it's kinda more advanced.

27 January 2012, 17:02	#1
Articat Posts: n/a	Classic WB 3.9 and PPC + Bvision problem? I have a problem with the Classic WB 3.9 pack. My system is a A1200 with Blizzard PPC 060@50 and 330mhz, I also have a Bvision and 128megs of RAM. When I do a regular clean install of WB 3.9 and the 060/PPC libs on my 8gig CF card on Winuae, and the puts it back on my amiga, everything works just fine. But when I try to do the same with classic WB 3.9 pack, the HDD lamp flashes for one second and the the powerlamp starts to blink and the computer resets and repets this cycle forever. My question now is, do I need some special LIB or driver if I have a PPC card and wanna use this wonderful WB pack? Maybe some of you guys have a PPC card and have experience the same thing? The Fblitter and Copper is off. Regards

27 January 2012, 17:19	#2
Bloodwych Moderator Join Date: Jun 2001 Location: I'm behind you! Posts: 3,763	I don't have definite answer myself - all I can suggest is disabling more of the components under the Settings menu (eg cyberBugFix, magic menu, tools daemon etc) to try and get it back to as close as a default install as possible then install your drivers and re-enable one at a time. However it sounds more like a setpatch issue if it's doing it from the off - check that the setpatch options are correct for your hardware in the startup-sequence file. By default, it loads the scsi.device driver for large hard drive support. Your hardware may need a different driver than the standard BB2 one in the ClassicWB. Hopefully someone with similar hardware can help you out. I only work in WinUAE and on a standard A1200 with fastram. Last edited by Bloodwych; 27 January 2012 at 18:49.

05 February 2012, 20:26	#10
mfilos Paranoid Amigoid Join Date: Mar 2008 Location: Athens/Greece Age: 45 Posts: 1,978	Ok... this version is the scsi.device version that exists inside the file "AmigaOS ROM Update" under Devs that came with the BB2 update. Since a new scsi.device is loaded upon boot, you MUST remove/rename the scsi.device from Devs: since Bloodwych's Startup-Sequence searches for a scsi.device in Devs: and if it founds it, it tries to load it with LoadModule command! I guess that's a reason why the boot is having issues. If that doesn't work, just make the following trick to see what else there is to check. Edit Startup-Sequence and command the SetPatch line by putting a semicolon in front of it ( and then press enter and instead write the following command: Code: C:SetPatch NOROMUPDATE QUIET This command will bypass the BB2 update so no new scsi.device will load (alas Bloodwych's script will try and load his own scsi.device. Report back with the findings

06 February 2012, 20:56	#12
mfilos Paranoid Amigoid Join Date: Mar 2008 Location: Athens/Greece Age: 45 Posts: 1,978	OK i'm glad it works with this. By issuing the NOROMUPDATE option in SetPatch declaration you're not using the BB2 update to the BB2 version's ROM Modules: - bootmenu - console.device - exec.library - filesystem.resource - filesystem - ram-handler - scsi.device - shell They might not be important to you but some are nice to have. I'd suggest try the following SetPatch declaration instead (for testing it) Code: C:SetPatch SKIPROMMODULES scsi.device QUIET That will load all the BB2 updated ROM modules EXCEPT the scsi.device which will remain the default (or the one that gets updated by the LoadModule declaration). If your Amiga boots just fine with this, then you're set for sure

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
For Sale: Cyberstorm PPC 060 50mhz / PPC 330mhz + 128mb / OS4.1 Classic	fitzsteve	MarketPlace	2	18 June 2013 12:39
BVISION PPC questions...	keropi	support.Hardware	7	26 March 2013 19:49
Blizzard PPC 040/25 + PPC 603 @160mhz + SCSI + BVision	BippyM	MarketPlace	14	04 August 2006 12:42
Whdload and Bvision PPC	Giana	support.Games	7	29 October 2002 12:11
PPC and Bvision in desktop Amiga	Unregistered	support.Hardware	11	17 July 2002 18:21

27 January 2012, 18:46	#3
ancalimon Supernormal Join Date: Jul 2007 Location: Istanbul / Turkey Age: 43 Posts: 1,413	Here's what I remember: You need to have the latest powerpc.library (Warpup) and the latest ppc.library (emulated version). You need Warp3d and the latest CyberGraphx4 (with patches) You need to have blizkick with the necessary module to remove ppc.library from ROM. You also need something called bppcfix In my opinion: Don't use loadmodule stuff. Don't use hacks like fblit, ftext, etc... The only hack I used was MCP with some of its options turned off.

27 January 2012, 19:22	#4
mfilos Paranoid Amigoid Join Date: Mar 2008 Location: Athens/Greece Age: 45 Posts: 1,978	I have used just fine ClassicWB 3.9: - On my A1200's BPPC/BVision combo (CGX4) - On my A4000's CSPPC/PicassoIV combo (P96) - On my A4000's CSPPC/CVisionPPC combo (CGX4) - On my A4000's CSPPC/Grex/Voodoo2 combo (CGX4) ...without a single issue! Be sure to disable Fblit/Ftext, BlazeWCP, IconsBeFast, CyberBugFix. Also be sure to use the latest 060 libs for your card and you'll be fine.

27 January 2012, 20:11	#5
Articat Posts: n/a	Thanks for you answers! I belive Bloodwychis right, I changed the Scisi.device to latest update from cosmos and now the HDD lamp starts to blink, after one second there is a reboot and then the HDD lamp lights (not blink) and nothing happens. It works perfect in Winuae thou... I will try to install this on a 4gig CF card. Maybe it´s just sensitive with big CF cards?

27 January 2012, 20:55	#6
mfilos Paranoid Amigoid Join Date: Mar 2008 Location: Athens/Greece Age: 45 Posts: 1,978	Some versions of Cosmos SCSI.device along with Doobrey's AFAIK have some issues with PFS3? What filesystem are you using in your A1200's HD mate? I'd suggest to use SFS to be sure.

05 February 2012, 00:34	#7
Articat Posts: n/a	This is strange! I got it working with a sandisk 4GB card BUT when I try the 8GIG sandisk card with patched scisi.device the HDD CF card locks, and it just lights and stays lighten. When I swap back to ClassicWBADV 3.1 and a Blizzard 1260 on the same card everythings works just fine I cant figure out why it wont work with the 8gig card when i go for WB3.9? I use SFS

05 February 2012, 02:38	#8
mfilos Paranoid Amigoid Join Date: Mar 2008 Location: Athens/Greece Age: 45 Posts: 1,978	Open a CLI under the 3.9 version and issue "version scsi.device" and tell us what is showing

05 February 2012, 16:53	#9
Articat Posts: n/a	Thanks for the support I belive this could be solved pretty easy??? The version number is scsi.device 43.43

06 February 2012, 22:51	#13
ancalimon Supernormal Join Date: Jul 2007 Location: Istanbul / Turkey Age: 43 Posts: 1,413	You should use blizkick instead of setpatch to load at least some of those updates.

08 February 2012, 19:59	#15
mfilos Paranoid Amigoid Join Date: Mar 2008 Location: Athens/Greece Age: 45 Posts: 1,978	I guess you're now set mate! Nice Blizkick is just an nice application that just loads modules into Blizzard's flash memory. You can use it as you were making some custom ROM. Although... since it requires a reboot to load the appropriate modules into it's flash... I don't see any actual reason of using it instead of the LoadModule command. Sure it's faster and more hardcore... but dunno It's a nice feature for all Blizzard accelerators but it's kinda more advanced.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)