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
A3000 and 3.2 roms
Re: A3000 and 3.2 roms
did you try swapping them?
Re: A3000 and 3.2 roms
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.
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.
Re: A3000 and 3.2 roms
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.
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
- Posts: 316
- Joined: Sat Jun 18, 2011 11:22 pm
Re: A3000 and 3.2 roms
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.
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.