Amiga.org
Operating System Specific Discussions => Amiga OS => Amiga OS -- Application questions and support => Topic started by: rubenscarrilho on September 24, 2010, 09:38:36 PM
-
Hi I need help about using 160gb Hard Disk on Amiga 1200 with Amiga OS 3.9.
I would like to create 4 partitions:
- 1st with 4gb
- 2nd with 50gb
- 3rd with 50gb
- 4th with 50gb
I try using HDTools but doest work.
Thank you!
-
"Doesnt work" is not an appropiate error description. Please give more details.
You cannot use more than 137 GB / 128 GiB on the internal IDE controller unless you installed this: http://aminet.net/package/driver/media/SCSI4345p
-
Can you help to use this Patch, because I have no experience...
Thank you!
-
Again more details are needed. Read the Installation section of the readme file and then tell us which part you didn't understand.
Note that you need OS 3.9 already installed before you can apply the patch.
Make sure that your first partition is *smaller* than 4GiB, i.e. 4000 MB or something like that, otherwise it won't boot.
-
Things that works:
Works -> ExtractModule MODULE 12 TO RAM:a300.ld.strip
Works-> spatch -pa300.ld.strip[.NEVER].pch -oDEVS:scsi.device RAM:a300.ld.strip
Things that doent works:
NOT WORK -> LoadModule "DEVS:NCR scsi.device" DEVS:scsi.device L:Shell-Seg REVERSE NOREBOOT
I got this error: -> Loading DEVS:NCR scsi.device failed: object not found
Did you understand?
-
Things that works:
Works -> ExtractModule MODULE 12 TO RAM:a300.ld.strip
Works-> spatch -pa300.ld.strip[.NEVER].pch -oDEVS:scsi.device RAM:a300.ld.strip
Things that doent works:
NOT WORK -> LoadModule "DEVS:NCR scsi.device" DEVS:scsi.device L:Shell-Seg REVERSE NOREBOOT
I got this error: -> Loading DEVS:NCR scsi.device failed: object not found
Did you understand?
Use : LoadModule DEVS:scsi.device L:Shell-Seg REVERSE NOREBOOT
You don't have or need the NCR scsi.device in an A1200.
-
I got this error.
LoadModule DEVS:scsi.device L:Shell-Seg REVERSE NOREBOOT
shell version 45 already resident.
Loading shell failed: object already exists
Sorry !
-
I haven't used my A1200s for years (and my primary one has a Power Flyer IDE adapter), but why not just set up the 4GB partition first (and leave the rest alone), get OS3.9 installed and working on that and worry about installing other file systems & patches and creating the large partitions?
That's what I did on my A4000 with an 80GB drive, then once the drive was partitioned (with SFS) I copied the whole contents from the 4GB FFS partition onto a 35GB SFS partition, changed the boot priorities and was done. I kept the basic install on the 4GB partition as an "emergency boot".
-
By the way do you have AmigaOS 3.9 with Boing Bag 1 and Boing Bag 2 WB updates installed. Maybe thats is why the last command is failing?
-
Mongo Use : LoadModule DEVS:scsi.device L:Shell-Seg REVERSE NOREBOOT
This line was just what I was looking for myself to use with using a 16GB SD card
with CF adapter. Soon as it executed... Bingo DH1 and DH2 showed
on the screen 7.6GB each
Thank you so much Mongo
evermore :roflmao:
-
I don't think I would want my System partition 4Gb. I would probably make it 500Mb, big enough for every system patch in the world and then some. Put everything else in other partitions, That would mean you won't be in the System writing all the time and so less chance to muck it up.
-
I don't think I would want my System partition 4Gb. I would probably make it 500Mb
+1. You don't want to risk coming across some outdated software that actually trashes the system partition, expecting it to be smaller.
-
You should make a 1mb custom kickstart using mfilos guide. That way you woun't have those problems. http://www.mfilos.com/2010/12/guide-create-and-burn-custom-kickstart.html
That guide has 2 problems, if you are intrested just ask.
SCSI device has a 127gb limit and usually it has problems Awith hds bigger than that.
-
Hi I need help about using 160gb Hard Disk on Amiga 1200 with Amiga OS 3.9.
I would like to create 4 partitions:
- 1st with 4gb
- 2nd with 50gb
- 3rd with 50gb
- 4th with 50gb
I try using HDTools but doest work.
Thank you!
Well, I also use a 160 gB harddisk in my Amiga4000PPC with OS 3.9.
Just that I use PFS3 as file system instead of FFS.
PFS3 doesn't have the 4 gB limitation, but it is commercial and I don't know where you could get it nowadays, aside from the electric bay...
;)
EDIT:
I just saw it is on Aminet these days:
PFS3_53 on Aminet (http://aminet.net/package/disk/misc/PFS3_53)
-
There is still a 128gb limit with scsi.device?
Having a big hard drive with original 3.1 roms is pure luck, some drives doesn't work at all and some does.
As said you need to have 4gb or smaller boot partitio and after you have installed a OS, you need to patch scsi.device and fastFileSystem or use another filesystem.
As far as I know this is only scsi.device for standard A1200 ide wich works with any size hard drives.
http://aminet.net/package/driver/media/SCSI4345p
I have selfmade 1mb kickstart rom with that scsi.device and all possible filesystems.
This 400gb hard drive didn't work at all with 3.1 kickastart
-
There is still a 128gb limit with scsi.device?
Having a big hard drive with original 3.1 roms is pure luck, some drives doesn't work at all and some does.
As said you need to have 4gb or smaller boot partitio and after you have installed a OS, you need to patch scsi.device and fastFileSystem or use another filesystem.
As far as I know this is only scsi.device for standard A1200 ide wich works with any size hard drives.
http://aminet.net/package/driver/media/SCSI4345p
I have selfmade 1mb kickstart rom with that scsi.device and all possible filesystems.
This 400gb hard drive didn't work at all with 3.1 kickastart
Boot partition must be no larger than 1.9GB unless you're running a physical custom Kickstart rom with an updated scsi.device. I don't know the specific exact capacity, but personally if you must have a large boot partition then 1GB should be much more than any Amiga could ever need and so I'd choose 1GB.
Years ago, my boot partition was 10MB in the 90's. Now days, I'd probably make it 256MB as it's a nice round number. :)
Even though you have a custom Kickstart rom, the danger is that you could be soft-kicking 2.0 or 3.0 which will not have the updated scsi.device, and you could find yourself trashing your boot partition if you write any data to it. My advice... Keep it at 1GB (or 1.9GB).
-
My boot partition is 28gb :) I don't have any reason to softkick my amiga to previous kickstart. How ever BB1/BB2 scsi.device works, I forget to rename romupdates / add skipromupdates in first boot.
-
All this everlasting nonsense support regarding large disks could be avoided if Cloanto could sell updated kickstart chips, and we could just tell everyone with a large disks to buy new kickstarts. I cannot fathom why this is not done!
-
There is still a 128gb limit with scsi.device?
Was there ever such a limit? Never experienced it...
Having a big hard drive with original 3.1 roms is pure luck, some drives doesn't work at all and some does.
Hmmm - let me think a moment:
I have two Kick3.1-A500s with Viper520 accelerator boards. On the Vipers there are 2.5" 320 mB harddrives - so no 4gB/128gB problem at all.
Then there is the towered Kick3.1-A1200 with IDEfix and 40 gB HD - also no problems - neither with 4gB, nor with 128gB (obviously not with just 40gB HD). Exceeding the 4gB limit is made possible by the TD64 device from the IDEfix 97 disk.
Finally there is the A4000 in Micronik BigTower with UW-SCSI host Adapter on the CSPPC, where my HDs are connected to. The HDs are 160gB (IDE via ACARD IDE->UW-SCSI bridge) and 4.3gB. Also no 4gB/128gB problems due to PFS3.
So far every harddrive I ever connected to my Kickstart 3.1 Miggies worked flawlessly out of the box - be it mfm/rll harddrives, IDE harddrives (2.5." and 3.5"), SCSI-II harddrives or UW-SCSI harddrives...
...
As far as I know this is only scsi.device for standard A1200 ide wich works with any size hard drives.
...
Hmmm - AFAIR, during the construction phase of my A4k tower, I had the 160 gB drive initially connected to the internal IDE port and was running OS 3.1 before I installed OS 3.5 and later 3.9.
I cannot remember of having experienced any scsi.device related problems - neither with OS 3.1, nor with OS 3.5 or 3.9 ...
This 400gb hard drive didn't work at all with 3.1 kickastart
Hmmm - on my Kick 3.1 A4kPPC I even connected an external 1 tB HD via USB to it - and it worked flawlessly.
-
My boot partition is 28gb :)
...
:eek:
Why does your boot partition have to be THAT big?
Normally 10 m[/i]B should suffice for the OS...
-
Was there ever such a limit? Never experienced it...
Hmmm - let me think a moment:
I have two Kick3.1-A500s with Viper520 accelerator boards. On the Vipers there are 2.5" 320 mB harddrives - so no 4gB/128gB problem at all.
Then there is the towered Kick3.1-A1200 with IDEfix and 40 gB HD - also no problems - neither with 4gB, nor with 128gB (obviously not with just 40gB HD). Exceeding the 4gB limit is made possible by the TD64 device from the IDEfix 97 disk.
Finally there is the A4000 in Micronik BigTower with UW-SCSI host Adapter on the CSPPC, where my HDs are connected to. The HDs are 160gB (IDE via ACARD IDE->UW-SCSI bridge) and 4.3gB. Also no 4gB/128gB problems due to PFS3.
So far every harddrive I ever connected to my Kickstart 3.1 Miggies worked flawlessly out of the box - be it mfm/rll harddrives, IDE harddrives (2.5." and 3.5"), SCSI-II harddrives or UW-SCSI harddrives...
Hmmm - AFAIR, during the construction phase of my A4k tower, I had the 160 gB drive initially connected to the internal IDE port and was running OS 3.1 before I installed OS 3.5 and later 3.9.
I cannot remember of having experienced any scsi.device related problems - neither with OS 3.1, nor with OS 3.5 or 3.9 ...
Hmmm - on my Kick 3.1 A4kPPC I even connected an external 1 tB HD via USB to it - and it worked flawlessly.
I think you must have Jay Miner watching over you :)
-
All this everlasting nonsense support regarding large disks could be avoided if Cloanto could sell updated kickstart chips, and we could just tell everyone with a large disks to buy new kickstarts. I cannot fathom why this is not done!
Just install IdeFix and be done with it.
-
Here, all limits wich are from filesystem and scsi.device.
http://eab.abime.net/showthread.php?t=61666
There shouldn't be any way use or see over 128gb limit with original or bb1/bb2 scsi.device
-
Just install IdeFix and be done with it.
I am not the problem here, I build my own kickstarts. The problem is the people who install large drives, constantly ask about this on forums, get a lot of confusing answers, mess around to get it right, somewhat randomly get it right eventually, only to mess up their filesystems later when booting without startup-sequence, or booting from floppy or whatever.