VOGONS


First post, by appiah4

User metadata
Rank l33t++
Rank
l33t++

This strange issue is driving me nuts.

Lucky Star 6P2BX2 board with Wimbios patched BIOS for HDD up to 128G
Pentium III 450 Slot 1
2x 128MB PC133 CL7 RAM
Voodoo 3 3000 AGP
Creative SB Live Value CT4780
Seagate 7200.8 Barraccuda 80G IDE
NEC 16x DVD-RW
USB keyboard

Partitioned the harddrive with gparted live cd and set a 4gb primary Fat32 as bootable.
Ran WinMe setup and it formatted the primary partition.
Ran scandisk and found empty space misreported. Fixed it.
Went to black screen, Copying files needed for setup message and hangs.

I said wat and immediately blamed Me so I tried installing 98SE instead.
Setup found the formatted primary partition, scanned it and ran scandisk reporting there were issues with the FAT so it would reveet latest changes to prior state.
Went to black screen, Copying files needed for setup message and hangs.

Booted WinMe command prompt ran fdisk /mbr then fdisk to delete all partitions and repartition in case gparted fucked up.
Tried to reinstall, same issue.
Booted WinMe command prompt to manually format C: only to find the 4G partition shows up as 3.2G after format and realized it might be a cluster size issue.. Ran fdisk to wipe partitions AGAIN and reduce primary partition to 2G.

Too tired so went to bed.

Most issues online seem to be caused by boot virus protection, people are advised to turn this off. My Award bios only has the Virus Warning option and its set to disabled (possibly works ass backwards abd I should enable it?). I will also try copyinf the files to the HDD to try installing from there.

Open to all suggestions..

Retronautics: A digital gallery of my retro computers, hardware and projects.

Reply 1 of 16, by Ampera

User metadata
Rank Oldbie
Rank
Oldbie

Why are you using a 4GB partition on an 80GB drive?

Do the whole drive and come back.

Other things to try are using a different drive (maybe smaller too), different HBA, different optical drive.

Reply 2 of 16, by appiah4

User metadata
Rank l33t++
Rank
l33t++
Ampera wrote:

Why are you using a 4GB partition on an 80GB drive?

Do the whole drive and come back.

Other things to try are using a different drive (maybe smaller too), different HBA, different optical drive.

I also set up the rest of the drive as a single extended partition with multiple logical drives in it (including fat32, linux swap and ext4), so the rest of the drive is not empty. I reduced the primary partition to 2GB in case primary partitions over 3.2gb cause issues for FAT32 Win98/Me installs, but haven't had the chance to try that yet.

As a side note, I know that it's not motherboard, RAM, DVD-ROM or IDE cable related because I can boot and use multiple Linux Live CDs no issues. What remains is either the HDD being bad (unlikely, as linux can read, partition and install onto it fine..), patched BIOS issue (again, unlikely, works fine in Linux) or some stupid Windows issue (most likely, but what it is I have no idea)..

Retronautics: A digital gallery of my retro computers, hardware and projects.

Reply 3 of 16, by Jorpho

User metadata
Rank l33t++
Rank
l33t++

Did you let the BIOS automatically detect the hard drive parameters, or did you input them manually? I've seen strange behavior when the parameters weren't auto-detected. Also, is the drive jumpered correctly, e.g. master with no slave present? (Avoid Cable Select.)

Reply 4 of 16, by appiah4

User metadata
Rank l33t++
Rank
l33t++
Jorpho wrote:

Did you let the BIOS automatically detect the hard drive parameters, or did you input them manually? I've seen strange behavior when the parameters weren't auto-detected. Also, is the drive jumpered correctly, e.g. master with no slave present? (Avoid Cable Select.)

IDE Auto Detection finds the drive as a proper 80GB and that's how it was set up.

The HDD is master and DVD-ROM is Slave, they work fine under Linux live distributions..

Retronautics: A digital gallery of my retro computers, hardware and projects.

Reply 5 of 16, by cyclone3d

User metadata
Rank l33t
Rank
l33t

Scandisk finding issues with the FAT every time you try to install sounds like a drive that is going bad to me.

I would definitely try a different drive.

It could also possibly be a bad stick of RAM.

Yamaha YMF modified setupds and drivers
Yamaha XG resource repository - updated November 27, 2018
Yamaha YMF7x4 Guide
AW744L II - YMF744 - AOpen Cobra Sound Card - Install SB-Link Header
Epstein didn't kill himself

Reply 6 of 16, by Ampera

User metadata
Rank Oldbie
Rank
Oldbie

Paritions over 3.2 GB don't have issues with FAT32. IIRC, It's 32 GB and that's only for LBA issues with machines that can't actually address a drive that big.

On that machine you should be fine up to around 130GB for disk size, and FAT32 is fine up to 2, to even 16 TiB in some cases.

Reply 7 of 16, by chinny22

User metadata
Rank l33t
Rank
l33t

yeh scandisk finding errors each time, on a new partition isn't a good sign.
Can imagine Linux being more forgiving then win9x

I would partition the fist drive with fdisk (MS should be fine with a MS created partition)
Just leave the rest of the drive unallocated, for the time being. Install windows.
You can then create the extended partition with gparted or fdisk. after windows is installed.

Reply 8 of 16, by appiah4

User metadata
Rank l33t++
Rank
l33t++

Installation works fine with 2GB Primary partition, WinMe installed 100% fine today. Out of curiosity I deleted the whole PT and repartitioned for 4096MB primary and the install hanged at the same spot with the same symptoms.

I do not know what it is, but with this board, and this BIOS, Win9x/Me refuse to install onto partitions larger than 3.2Gb (max partition size for 8K cluster size IIRC). It doesn't mind having an extended partitions of 74Gb though.

I will leave this here for the sake of anyone who goes nuts trying to figure something similar out: Try a partition size smaller than 3.2Gb.

Retronautics: A digital gallery of my retro computers, hardware and projects.

Reply 9 of 16, by 95DosBox

User metadata
Rank Member
Rank
Member
Ampera wrote:

Paritions over 3.2 GB don't have issues with FAT32. IIRC, It's 32 GB and that's only for LBA issues with machines that can't actually address a drive that big.

On that machine you should be fine up to around 130GB for disk size, and FAT32 is fine up to 2, to even 16 TiB in some cases.

Can you elaborate your setup for 16TiB on FAT32?

Reply 10 of 16, by 95DosBox

User metadata
Rank Member
Rank
Member
appiah4 wrote:

Installation works fine with 2GB Primary partition, WinMe installed 100% fine today. Out of curiosity I deleted the whole PT and repartitioned for 4096MB primary and the install hanged at the same spot with the same symptoms.

I do not know what it is, but with this board, and this BIOS, Win9x/Me refuse to install onto partitions larger than 3.2Gb (max partition size for 8K cluster size IIRC). It doesn't mind having an extended partitions of 74Gb though.

I will leave this here for the sake of anyone who goes nuts trying to figure something similar out: Try a partition size smaller than 3.2Gb.

It could be the age of the BIOS causing this. But if you can partition the first partition as 2GB FAT16 you should be fine. The rest is extended partition. Then you will have to create logical drives. I wouldn't recommend a drive say over 60GB for Windows 98 legacy system since it doesn't like it. FDISK doesn't work properly unless you get the updated version.

Reply 11 of 16, by mrau

User metadata
Rank Oldbie
Rank
Oldbie
95DosBox wrote:
Ampera wrote:

Paritions over 3.2 GB don't have issues with FAT32. IIRC, It's 32 GB and that's only for LBA issues with machines that can't actually address a drive that big.

On that machine you should be fine up to around 130GB for disk size, and FAT32 is fine up to 2, to even 16 TiB in some cases.

Can you elaborate your setup for 16TiB on FAT32?

whats the cluster size on that?

Reply 12 of 16, by Jorpho

User metadata
Rank l33t++
Rank
l33t++

16 terabytes = 17,592,186,044,416 bytes

Divide by 2^32 = 4,294,967,296 and you get 4,096, so 4K clusters.

(In comparison, 2 GB = 2,147,483,648 bytes; divide by 2^16 = 65536, and you get 32,768, the 32K cluster size of a 2 GB FAT16 partition.)

Reply 13 of 16, by ketling

User metadata
Rank Newbie
Rank
Newbie
appiah4 wrote on 2017-05-15, 05:36:

Went to black screen, Copying files needed for setup message and hangs.

I had the same issue and the same way I tried everything for several days. Changing HW, BIOS settings, different CDs and so on. One thing that finally worked for me was to run the Windows setup with /iq switch. "/IQ. Skips the check for cross-linked files".

Reply 15 of 16, by Horun

User metadata
Rank Oldbie
Rank
Oldbie
appiah4 wrote on 2017-05-15, 07:50:

I also set up the rest of the drive as a single extended partition with multiple logical drives in it (including fat32, linux swap and ext4), so the rest of the drive is not empty. I reduced the primary partition to 2GB in case primary partitions over 3.2gb cause issues for FAT32 Win98/Me installs, but haven't had the chance to try that yet.

As a side note, I know that it's not motherboard, RAM, DVD-ROM or IDE cable related because I can boot and use multiple Linux Live CDs no issues. What remains is either the HDD being bad (unlikely, as linux can read, partition and install onto it fine..), patched BIOS issue (again, unlikely, works fine in Linux) or some stupid Windows issue (most likely, but what it is I have no idea)..

Sounds like the Wims BIOS large HD fix created an odd issue that the older original BIOS with 8Gb limit may not have = 3Gb primary partition maximum. My old Asus P2B has 137Gb support as of bios 1013, prior to that you could create a Primary of 8gb without issue, not 3Gb. I would go back to the original BIOS and try Disk Manager or Drive Pro to use the LBA overlay. Yes not the best alternative but without a true Lucky Star 6P2BX2 released BIOS that supports large HD there could also be other BIOS issues unseen yet in that "hacked" bios.

Hate posting a reply and have to edit it because it made no sense 😁 First computer was an IBM 3270 workstation with CGA monitor. 🤣

Reply 16 of 16, by darry

User metadata
Rank Oldbie
Rank
Oldbie
Horun wrote on 2020-05-24, 03:06:
appiah4 wrote on 2017-05-15, 07:50:

I also set up the rest of the drive as a single extended partition with multiple logical drives in it (including fat32, linux swap and ext4), so the rest of the drive is not empty. I reduced the primary partition to 2GB in case primary partitions over 3.2gb cause issues for FAT32 Win98/Me installs, but haven't had the chance to try that yet.

As a side note, I know that it's not motherboard, RAM, DVD-ROM or IDE cable related because I can boot and use multiple Linux Live CDs no issues. What remains is either the HDD being bad (unlikely, as linux can read, partition and install onto it fine..), patched BIOS issue (again, unlikely, works fine in Linux) or some stupid Windows issue (most likely, but what it is I have no idea)..

Sounds like the Wims BIOS large HD fix created an odd issue that the older original BIOS with 8Gb limit may not have = 3Gb primary partition maximum. My old Asus P2B has 137Gb support as of bios 1013, prior to that you could create a Primary of 8gb without issue, not 3Gb. I would go back to the original BIOS and try Disk Manager or Drive Pro to use the LBA overlay. Yes not the best alternative but without a true Lucky Star 6P2BX2 released BIOS that supports large HD there could also be other BIOS issues unseen yet in that "hacked" bios.

An IDE or SATA PCI controller which supports at least LBA28 (or LBA48 for "future" proofing) is also an option .