Drives in HDToolBox not detected full size (CHS settings?)

[Thomas]

My 3.9 installation is missing some stuff

More details needed.

the 3.1 installation said (never did before) that my 2GB partition didn't have enough room for Fonts.

Then the partition is bigger than 2GB. For 3.1 everything above 2 GB is negative. Put some big files on the partition so that free space shrinks below 2 GB. After installation these files can be deleted.

I'm assuming one of the benefits is less confusing size issues, but what others?

A new scsi.device does not fix bugs in HDToolbox and other programs, therefore size issues won't change.

[nyteschayde]

Thomas is right. The scsi.device seems function both better as well as provide functionality such as exposing the secondary IDE device on a chained cable but it will not patch tools with rendering and math bugs like HDToolbox.

[LoadWB]

Right, right, I was not thinking problems with HDToolBox, but that it would support TD64 as well as NSD (but then again, isn't NSD the preferred one over TD64?) and wasn't detecting larger drives a problem with scsi.device.  Not seeing the calculated sizes properly, but just seeing the drives period.

In any case, my partition was 1.8GB (supposedly) and the installation reported not enough space for Fonts, and after the 3.9 upgrade, in particular, resource.library is missing.  Some functionality is broken, as well, but I was in too much of a hurry to really remember which -- my thought was, the installation was broken to begin with as evidenced by the Fonts problem.

I have to re-install the drive with proper geometry, anyway, so everything on it is a lost cause.

But I'm not going to have it in-hand again until Tuesday.  I *may*, however, work with my CSMKIII system with a SCSI-to-IDE/IDE-to-SATA adapter to install an SSD in that.  Maybe.  Have to upgrade my Core2Quad to a Gen7-i7 this weekend, too.  So much to do, so little time.

[nyteschayde]

The scsi.device v52 seems to sort out a lot of the wonkiness I needed other tools for and it is loaded resident. So imho it's a win-win. Your mileage may vary but so far it has treated me well

[LoadWB]

The scsi.device v52 seems to sort out a lot of the wonkiness I needed other tools for and it is loaded resident. So imho it's a win-win. Your mileage may vary but so far it has treated me well

Worth the purchase, then.  I have been debating and convinced myself out of buying OS4.1 until I actually get a PPC accelerator.  This gives more support to the side of "buy now."

[Oldsmobile_Mike]

scsi.device from 4.1 works with 3.9?

[RiP]

Remember I used gvpscsi.device with HDtoolbox in WB2.05 but it couldn't detect my 500mb scsi hdd but no problem with an old 50mb one.
So I used the GVP floppy installation utility and detected without problem.

[Rotzloeffel]

scsi.device from 4.1 works with 3.9?

Yes, the scsi.device FROM THE BOOTFLOPPY !

[LoadWB]

Today was taken up by a dead server and its replacement and errands before I left town... and I have, so I will get back to this in a couple of weekends.

[nyteschayde]

scsi.device from 4.1 works with 3.9?

Yes it even works with 3.1. The one from the boot floppy. Additionally the atapimajik file from devs: and the cdmounter util from c: on the same floppy will easily mount any attached ide CD-ROM. Merry Christmas. Two files for easy and fairly complete cd-rom drivers is also pretty damn awesome.

[nyteschayde]

Always check the c,l,s,devs,libs and fonts directory of every bootable. Tons of treasures to be found.

[Pat the Cat]

Always check the c,l,s,devs,libs and fonts directory of every bootable. Tons of treasures to be found.

Pretty good advice. Although it's more dirt than nuggets... most of the time.

I'm not TOO surprised about a .device file running retroactively, on an earlier release. Hardware device drivers are like software libraries for hardware outside of the core basic computer system - so they are more tied to the extra hardware then they are to the core.

Mind you, I must admit I rarely tried this, except as a last resort. Seems counter intruitive. And it doesn't always work, because sometimes the extra hardware is tied down to a further OS by library use or another factor, which is bound to the core in some way.

[LoadWB]

The correct CHS numbers helped, but not totally.  No matter what I have tried, OS3.9 will not correctly install on this KingSpec 64GB SSD.  I am going to try the 128GB but I have no reason to be confident of success over the 64GB.

I created a 1GB partition at the beginning of the drive with no other partitions.  Formatted this QUICK with FFS 45.9.  The installation of 3.1 completed with no apparent problems, but 3.9 installation missed icons, libraries, and probably more without any errors during the installation.  I tried performing an installation of 3.9 from the 3.9 emergency-boot but I get the can't get Workbench information error.

[Oldsmobile_Mike]

but 3.9 installation missed icons, libraries, and probably more without any errors during the installation

I had a problem with 3.9 once that was missing files, this was due to a dodgy CD.  Possible to try a different installation media?  Although AFAIR it did throw errors when it encountered scratches on the CD...

[nyteschayde]

The correct CHS numbers helped, but not totally.  No matter what I have tried, OS3.9 will not correctly install on this KingSpec 64GB SSD.  I am going to try the 128GB but I have no reason to be confident of success over the 64GB.

I created a 1GB partition at the beginning of the drive with no other partitions.  Formatted this QUICK with FFS 45.9.  The installation of 3.1 completed with no apparent problems, but 3.9 installation missed icons, libraries, and probably more without any errors during the installation.  I tried performing an installation of 3.9 from the 3.9 emergency-boot but I get the can't get Workbench information error.

Make sure you have the right max transfer speeds setup. I was getting random write errors and crashes on my A1200 without it. I think it's 0x01fe00 but double check that elsewhere first.

[LoadWB]

Checked that, too.  Even worse, I just took a CF card and without re-initializing it just  partitioned and formatted and lo, the upgrade from 3.1 to 3.9 is corrupt.  Like Mike, I think I could be dealing with a bad 3.9 CD.  I don't know, but at this point I've spent several hours across three drives.  I'll try again next week.