classicwb 3.9 trouble

Liquidsnake · 29 September 2014, 00:58

Hi guys!

Doesn anyone here know if certain hardrives are incompatible with classicwb 3.9 ?
I have a western digital 200gb, in my A4000D at the moment and while advsp runs without any trouble, classic 3.9 doesn't boot at all, gurus immediately.

I ask because I had a similar problem on my A1200 albeit with a cf-card, 3.9 wouldn't boot with a sandisk ultra 16-gig card, but with transcend 133x it worked perfectly.

Perhaps the odds of this being true are small but I thought I'd ask just in case

FOL · 29 September 2014, 01:29

Quote:

Originally Posted by Liquidsnake

Hi guys!

Doesn anyone here know if certain hardrives are incompatible with classicwb 3.9 ?
I have a western digital 200gb, in my A4000D at the moment and while advsp runs without any trouble, classic 3.9 doesn't boot at all, gurus immediately.

I ask because I had a similar problem on my A1200 albeit with a cf-card, 3.9 wouldn't boot with a sandisk ultra 16-gig card, but with transcend 133x it worked perfectly.

Perhaps the odds of this being true are small but I thought I'd ask just in case

If it guru's straight away, check that you have the correct filesystem in the RDB.

Liquidsnake · 29 September 2014, 01:36

Quote:

Originally Posted by FOL

If it guru's straight away, check that you have the correct filesystem in the RDB.

I used sfs at that time, and I checked with check4gb before that everything checked out and it did

FOL · 29 September 2014, 03:33

Quote:

Originally Posted by Liquidsnake

I used sfs at that time, and I checked with check4gb before that everything checked out and it did

Boing Bag 2?
If so, try renaming the AmigaROMUpdate in the devs folder.

Liquidsnake · 29 September 2014, 11:39

Quote:

Originally Posted by FOL

Boing Bag 2?
If so, try renaming the AmigaROMUpdate in the devs folder.

Yeah BB1 and BB2 are required for classicwb to work so they're both installed on this setup.

Renaming it to what ?

Jope · 29 September 2014, 13:34

Add a dot in the end or something so that it isn't called AmigaROMUpdate any more and won't be loaded.

demolition · 29 September 2014, 13:50

Had the same issue and turned out the scsi.device in 3.9 doesn't work with many CF cards. Replace scsi.device with some other one (one that is fixed for >8G drives) and it should work.

Liquidsnake · 29 September 2014, 14:07

I don't think I actually installed the romupdate, you're talking about the one in boing bag 2 right ?

Liquidsnake · 29 September 2014, 14:36

Quote:

Originally Posted by demolition

Had the same issue and turned out the scsi.device in 3.9 doesn't work with many CF cards. Replace scsi.device with some other one (one that is fixed for >8G drives) and it should work.

I thought that 3.9 patched large partitions automatically ?

FOL · 29 September 2014, 14:43

Quote:

Originally Posted by Liquidsnake

I thought that 3.9 patched large partitions automatically ?

No. It still has to boot of 3.1 roms.

demolition · 29 September 2014, 14:50

Quote:

Originally Posted by Liquidsnake

I thought that 3.9 patched large partitions automatically ?

Yes, it has an updated scsi.device which works with larger partitions, however it does not work with CF cards, only real HDDs as far as I've found out. I replaced it with the patched scsi.device from my old CWB3.1 installation and it booted just fine.

Liquidsnake · 29 September 2014, 14:53

Quote:

Originally Posted by demolition

Yes, it has an updated scsi.device which works with larger partitions, however it does not work with CF cards, only real HDDs as far as I've found out. I replaced it with the patched scsi.device from my old CWB3.1 installation and it booted just fine.

Well, I ran classicwb 3.9 on my A1200 with pfs3aio on a 16-gig card, and it worked perfectly. It could be that you need a another cf-card, the sandisk ultra 16-gig didn't work for me but the transcend 133x did

demolition · 29 September 2014, 14:56

Quote:

Originally Posted by Liquidsnake

Well, I ran classicwb 3.9 on my A1200 with pfs3aio on a 16-gig card, and it worked perfectly. It could be that you need a another cf-card, the sandisk ultra 16-gig didn't work for me but the transcend 133x did

True, it might work with some CF cards, but I read somewhere that it is a lot more picky. I use a Sandisk Ultra 8GB and it works fine with both the regular and patched scsi.device, but not the one from WB3.9.

Liquidsnake · 29 September 2014, 15:03

Okidoki

Liquidsnake · 29 September 2014, 20:05

I've Renamed the one ROm update file, and I'm gonna try running a harddrive with sfs filesystem with cwb 3.9.

Liquidsnake · 29 September 2014, 20:33

Quote:

Originally Posted by FOL

No. It still has to boot of 3.1 roms.

Well, yeah you need 3.1 kicks to run 3.9, however the os itself handles large partitions (over 4gb) without patching the scsi.device

FOL · 29 September 2014, 22:06

Quote:

Originally Posted by Liquidsnake

Well, yeah you need 3.1 kicks to run 3.9, however the os itself handles large partitions (over 4gb) without patching the scsi.device

Not until it loads the patches.

demolition · 29 September 2014, 22:09

Quote:

Originally Posted by FOL

Not until it loads the patches.

True, so the boot drive can still not be any bigger unless you make your own custom kickstart.

Liquidsnake · 29 September 2014, 22:30

Quote:

Originally Posted by FOL

Not until it loads the patches.

Well yeah but I mean you don't have to yourself put a file in devs or anything like that

29 September 2014, 00:58	#1
Liquidsnake Registered User Join Date: Jan 2014 Location: Malmberget /Sweden Posts: 29	classicwb 3.9 trouble Hi guys! Doesn anyone here know if certain hardrives are incompatible with classicwb 3.9 ? I have a western digital 200gb, in my A4000D at the moment and while advsp runs without any trouble, classic 3.9 doesn't boot at all, gurus immediately. I ask because I had a similar problem on my A1200 albeit with a cf-card, 3.9 wouldn't boot with a sandisk ultra 16-gig card, but with transcend 133x it worked perfectly. Perhaps the odds of this being true are small but I thought I'd ask just in case

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
ClassicWB and floppy trouble	Solo761	project.ClassicWB	0	05 February 2014 21:11
Which OS - ClassicWB 3.1 ADVSP or ClassicWB 3.9?	MrGimper	support.Hardware	7	06 October 2010 11:10
Multiboot ClassicWB/3.1 and ClassicWB/OS3.9	MrGimper	support.Hardware	4	16 September 2010 19:42
Having trouble installing ClassicWB UAE	h4tt3n	support.WinUAE	3	05 February 2010 09:38
Trouble Installing ClassicWB	Tiddlypeeps	project.ClassicWB	11	22 January 2010 23:06

29 September 2014, 13:34	#6
Jope - Join Date: Jul 2003 Location: Helsinki / Finland Age: 43 Posts: 9,861	Add a dot in the end or something so that it isn't called AmigaROMUpdate any more and won't be loaded.

29 September 2014, 13:50	#7
demolition Unregistered User Join Date: Sep 2012 Location: Copenhagen / DK Age: 43 Posts: 4,190	Had the same issue and turned out the scsi.device in 3.9 doesn't work with many CF cards. Replace scsi.device with some other one (one that is fixed for >8G drives) and it should work.

29 September 2014, 14:07	#8
Liquidsnake Registered User Join Date: Jan 2014 Location: Malmberget /Sweden Posts: 29	I don't think I actually installed the romupdate, you're talking about the one in boing bag 2 right ?

29 September 2014, 15:03	#14
Liquidsnake Registered User Join Date: Jan 2014 Location: Malmberget /Sweden Posts: 29	Okidoki

29 September 2014, 20:05	#15
Liquidsnake Registered User Join Date: Jan 2014 Location: Malmberget /Sweden Posts: 29	I've Renamed the one ROm update file, and I'm gonna try running a harddrive with sfs filesystem with cwb 3.9.

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