A3000 and 3.2 roms

[Hotblack]

Hi

Just got my 3.2 rom's and the OS CD. I did not receive any instruction on how to install the rom's, For an unknown reason Hyperion marked the rom's with hi and lo and not the socket numbers, so uncertain if socket 180 should house hi or lo. I burnt a few custom rom's over the years, and then the 181 held lo.

Anyway I put them (yes the little notch to the left) the machine refuse to boot. I ordered the chips not to have to fiddle with EPROMs. Any suggestions of what I might gotten wrong. 3.1 rom's works perfectly when I reinstall them.

A3000 rev 6.3 the one with only 180 ans 181 is socketed

Thanks

[amifrog]

did you try swapping them?

[Hotblack]

Happy New Year.

Spent a week in bed with a whatever flu. Good to be selfmedicating myself to a waken state again.

Yes in fact I did try that in the hope that i had gotten hi and lo wrong, as i remember it will not ruin the rom's. Checked the 3.2 on my programmer and they are still okay.
I read somewhere that 181 should hold hi, but who knows. Stupid of Hyperion not to help out there by just printing U18X on them.

I just burned one 27c400 to my CDTV and I'm currently running OS3.2 on that. Even though the promised《4GB disk support is still illusive. 4GB micro SD it is for now.

Will try to burn new rom's to the 3000D later on and also try the ones i bought for the 4000D.

[Hotblack]

Hi there,

It seems this forum is a bit inactive. But well, I have my A3000 up and running on 3.2 Rom's (yes you MUST have a disk drive DF0: installed or it wont boot, contrary to the A4000 that can live without a drive upon boot. A painful learning before I realized that )

Why do I still have the same problem as on the CDTV and a perfectly functioning 8GB Micro SD Sundisk (on a SCSI to MicroSD board), is not formattable? I have chunked the disk up to 4 x <2GB partitions.

Wasn't OS3.2 suppose to fix and bridge this barrier? That was one of the USP's if I recall the hype. I have a 8GB drive on native IDE port on my A4000 and it does just fine. I have a 32GB SD on my A1200 and that machine does never have any issues whatsoever.

I have tried a FAST-ATA card on the A3000 and that works, but feels like a waste. The native SCSI is fast enough for me at least. I have tried a Cyberstorm PPC card and there are no boundaries of disk size there (at least not up to my needs)

So what is the thing with OS3.2 and the 4GB barrier? Is it that the disk cannot be larger than 4GB in total no matter what the partition size?

Thanks for any help here.

[thomasrapp]

You have to be more concrete about what you mean by "not formattable".

There is no disk size limit in SCSI, there never was. What is new in 3.2 is that the native file system supports large harddisks, too. With other file systems, for example PFS3, you could do the same in earlier OS versions, too. Even on Kick 1.3.

As a proof I just created a 5000 MB WB_2.x partition with FFS Long Filenames and put Kick 47.111 into Devs/Kickstart. It boots perfectly on the original A3000 Kick 1.4. All I had to do is to enable "Direct SCSI Transfer" in HDToolbox. With a physical Kick 3.2 I do not even need that.

[Hotblack]

Hi Thomas,

Sorry for not answering. I have put this project on the shelf for a while, and just restarted and found your post.

Let me try to be more specific:

I have a SCSI to Micro SD adaptor card on a fairly stock A3000 (16MB RAM). The MicroSD card is a 8GB Sundisk (but I tried other 8GB cards as well). All my SCSI disk drives are bad or at end of lifecycle so I have to find find more reliable future proof solutions.

I have tried FFS that comes with OS3.2. I have tried PFS3 (DS version) with activated Direct SCSI option (I get the PSF3DS when selecting filesystem ID 50445303 or whatever it is). In WinUAE I can partition and format the complete 8GB in all possible partitions, but on the A3000 only the first 4GB can be used.

I can format lets say DH0 500MB, a programs DH1 of 3,5GB, but nothing beyond that. If I for example make a DH2 of 500mb, 1Gb, 2GB or 4GB it's all doable in HDToolbox, but after saving and eventual reboot I cannot format the drive. When selecting for example DH2 (sitting above the 4GB zone) and chose format, I get the normal warnings of lost data and lastly the PFS3 pop-up but then I get "write error 5 on block 0", and after closing that window it throughs "Device DH2: LRU update failed" and goes into a loop, and I can click OK a thousand times but never get out. It just re-pops up the same window endlessly.

I have tried two different version of the SCSI to Micro SD adaptor cards and I have the same result on the CDTV. I have read multiple guides (and many of your posts in different forums too) on how to set PFS3 up and I have also tried PFSAIO. I have tried with or without Direct SCSI and I have tried 1GB, 2GB and 4GB. all those works fine. I have tried 8GB, 16GB and 32GB Micro SD cards, and none of those works above 4GB and if I only use those 4GB the drive seems to read and write unreliably.

I have used the original WDC-04 SCSI chip and I have currently the "less buggy" WDC-08 chip.

4GB is too small to get all programs, ADF's and stuff onto a disk and 8GB would be so perfect.

I must do something fundamentally wrong here, since many users reports they are successful.

You seem to know a lot, if not everything worth knowing about drives in general, but have you encountered this?

Best regards, and thank you for posting in the first place. I will check in more frequently in the future.

Thanks a lot.

[thomasrapp]

I have tried PFS3 (DS version)

Please try again with pfs3aio
https://aminet.net/package/disk/misc/pfs3aio

then I get "write error 5 on block 0"

There will be more info in the message with pfs3aio. In any case it is some unexpected SCSI error which means there is something wrong with the hardware.