VOGONS


Post, no boot issue. Ep. 2

Topic actions

First post, by Alistar1776

User metadata
Rank Member
Rank
Member

so, new Socket 370 system with a PIII. basically moved the drive with working windows 98 se and most the cards from the old Slot 1 AMD system to the new one, was able to boot into Windows 98 a few times, but will no longer boot. I dont understand why, my theory has to do with graphics, as even tho the gpu was transferred to the new machine, i suppose the drivers didnt reinstall quite right. not sure 100% tho. Ive been thru the bios on the board, its a gigabyte GA-6VXE7+ couldnt find anything thatll let it boot to windows, maybe i missed something. it gets to the point in the boot sequence it should be launching windows and just sits with a cursor. tried swapping a cable too, no luck.

Reply 2 of 22, by AppleSauce

User metadata
Rank Oldbie
Rank
Oldbie

Hmm I've been planning on migrating from an abit bf6 to an asus p3b-f so ill keep tabs on this thread.

I figured there would be some hiccups along the way so I havent gotten around to doing it yet , im guessing uninstalling the original chipset drivers beforehand and installing the correct chipset drivers after migration might be necessary right?

Anyone else successfully pulled off what op is trying to accomplish?

Reply 3 of 22, by Alistar1776

User metadata
Rank Member
Rank
Member
weedeewee wrote on 2022-12-25, 08:01:

have you tried safe mode ?

i dont get the option to boot safe mode

it goes thru the boot process, detecting the drives, finding pci devices, then gets to "Verifying DMI Pool Data........" and hangs there. all i get to.

sometimes it does
"Updating ESCD...... Success
Verifying DMI Pool Data..... Success"
and then hangs there. like it cant boot for some reason.

Reply 4 of 22, by darry

User metadata
Rank l33t++
Rank
l33t++
Alistar1776 wrote on 2022-12-25, 18:13:
i dont get the option to boot safe mode […]
Show full quote
weedeewee wrote on 2022-12-25, 08:01:

have you tried safe mode ?

i dont get the option to boot safe mode

it goes thru the boot process, detecting the drives, finding pci devices, then gets to "Verifying DMI Pool Data........" and hangs there. all i get to.

sometimes it does
"Updating ESCD...... Success
Verifying DMI Pool Data..... Success"
and then hangs there. like it cant boot for some reason.

That's not a Windows or even DOS issue. If it fails there, it wouldn't even boot from a floppy .

Suggestions :

Try resetting PnP ESCD data in BIOS . Also, try resetting BIOS defaults.
If that all fails, try stripping the system down to minimum (remove all cards not required to boot) and see if that helps.

Reply 5 of 22, by Alistar1776

User metadata
Rank Member
Rank
Member
darry wrote on 2022-12-25, 19:42:
That's not a Windows or even DOS issue. If it fails there, it wouldn't even boot from a floppy . […]
Show full quote

That's not a Windows or even DOS issue. If it fails there, it wouldn't even boot from a floppy .

Suggestions :

Try resetting PnP ESCD data in BIOS . Also, try resetting BIOS defaults.
If that all fails, try stripping the system down to minimum (remove all cards not required to boot) and see if that helps.

ok. Ive reset bios to defaults, and stripped it to a barebones config, and it still just sits there. It does boot to a floppy. I then set the bios to reset escd and dmi, rebooted, and its still sitting there says
"Updating ESCD ... Success
Building DMI Pool ................ Success
Verifying DMI Pool Data ....... Update Success
_"

update: tried another hdd, and it didnt just sit there, it actually popped up "invalid system disk" which, given the drive is empty, is expected.

Reply 6 of 22, by weedeewee

User metadata
Rank l33t
Rank
l33t

with the original hdd in the machine, try booting from floppy, and verify you have access to the files on the hard drive.
if yes, then try an 'fdisk /mbr' and reboot from hdd if possible.
if it still hangs... boot from floppy again with the same dos/windows version as is present on the hdd and do a 'sys c:' then reboot.
if you do not have access to the files on the hdd... i'll have to think about it some more.

Right to repair is fundamental. You own it, you're allowed to fix it.
How To Ask Questions The Smart Way
Do not ask Why !
https://www.vogonswiki.com/index.php/Serial_port

Reply 7 of 22, by Alistar1776

User metadata
Rank Member
Rank
Member
weedeewee wrote on 2022-12-25, 20:33:
with the original hdd in the machine, try booting from floppy, and verify you have access to the files on the hard drive. if yes […]
Show full quote

with the original hdd in the machine, try booting from floppy, and verify you have access to the files on the hard drive.
if yes, then try an 'fdisk /mbr' and reboot from hdd if possible.
if it still hangs... boot from floppy again with the same dos/windows version as is present on the hdd and do a 'sys c:' then reboot.
if you do not have access to the files on the hdd... i'll have to think about it some more.

booting to the win98se boot floppy, and i cannot see the files on the drive... it says
"Invalid media type reading drive C
Abort, Retry, Fail?"
running fdisk and looking at partition info, it says pri-dos partition.... sssooooooo idk what thats about

Reply 8 of 22, by weedeewee

User metadata
Rank l33t
Rank
l33t

I can only guess that somehow some data on the hdd got corrupted.
Considering the move from amd to intel, I'm guessing chipset and/or IDE drivers screwed something up.
if it was a CF card and not a hdd, I'd say the dma mode caused some data corruption.

Now fixing this mess. no idea at the moment. the christmas spirits are taking their toll.

Right to repair is fundamental. You own it, you're allowed to fix it.
How To Ask Questions The Smart Way
Do not ask Why !
https://www.vogonswiki.com/index.php/Serial_port

Reply 9 of 22, by Alistar1776

User metadata
Rank Member
Rank
Member
weedeewee wrote on 2022-12-25, 21:35:
I can only guess that somehow some data on the hdd got corrupted. Considering the move from amd to intel, I'm guessing chipset […]
Show full quote

I can only guess that somehow some data on the hdd got corrupted.
Considering the move from amd to intel, I'm guessing chipset and/or IDE drivers screwed something up.
if it was a CF card and not a hdd, I'd say the dma mode caused some data corruption.

Now fixing this mess. no idea at the moment. the christmas spirits are taking their toll.

🤣 i gotcha. Ive attempted to reinstall the OS, starting from scratch, but either the default drivers for the cdrom arent loading, or when that does work, it cant find the setup files on the disk. Im very frustrated with it atm 🤣.

Reply 10 of 22, by darry

User metadata
Rank l33t++
Rank
l33t++
Alistar1776 wrote on 2022-12-25, 22:07:
weedeewee wrote on 2022-12-25, 21:35:
I can only guess that somehow some data on the hdd got corrupted. Considering the move from amd to intel, I'm guessing chipset […]
Show full quote

I can only guess that somehow some data on the hdd got corrupted.
Considering the move from amd to intel, I'm guessing chipset and/or IDE drivers screwed something up.
if it was a CF card and not a hdd, I'd say the dma mode caused some data corruption.

Now fixing this mess. no idea at the moment. the christmas spirits are taking their toll.

🤣 i gotcha. Ive attempted to reinstall the OS, starting from scratch, but either the default drivers for the cdrom arent loading, or when that does work, it cant find the setup files on the disk. Im very frustrated with it atm 🤣.

I was under the impression that it froze BEFORE trying to actual boot from HDD, but I was apparently wrong .

What capacity are each of the hard drives you tried and what are the motheboards and their installed BIOS revisions ?

Maybe the BIOSes use different sector translation schemes (wiping the partition table might be something to try) and/or the P3 BIOS can't handle drives beyond a certain capacity .

Last edited by darry on 2022-12-25, 22:15. Edited 1 time in total.

Reply 11 of 22, by weedeewee

User metadata
Rank l33t
Rank
l33t
Alistar1776 wrote on 2022-12-25, 22:07:

🤣 i gotcha. Ive attempted to reinstall the OS, starting from scratch, but either the default drivers for the cdrom arent loading, or when that does work, it cant find the setup files on the disk. Im very frustrated with it atm 🤣.

Oh yeah, I know that feeling all too well ! Enjoy the festivities & good luck ! 😀

Right to repair is fundamental. You own it, you're allowed to fix it.
How To Ask Questions The Smart Way
Do not ask Why !
https://www.vogonswiki.com/index.php/Serial_port

Reply 12 of 22, by Alistar1776

User metadata
Rank Member
Rank
Member
darry wrote on 2022-12-25, 22:14:
I was under the impression that it froze BEFORE trying to actual boot from HDD, but I was apparently wrong . […]
Show full quote
Alistar1776 wrote on 2022-12-25, 22:07:
weedeewee wrote on 2022-12-25, 21:35:
I can only guess that somehow some data on the hdd got corrupted. Considering the move from amd to intel, I'm guessing chipset […]
Show full quote

I can only guess that somehow some data on the hdd got corrupted.
Considering the move from amd to intel, I'm guessing chipset and/or IDE drivers screwed something up.
if it was a CF card and not a hdd, I'd say the dma mode caused some data corruption.

Now fixing this mess. no idea at the moment. the christmas spirits are taking their toll.

🤣 i gotcha. Ive attempted to reinstall the OS, starting from scratch, but either the default drivers for the cdrom arent loading, or when that does work, it cant find the setup files on the disk. Im very frustrated with it atm 🤣.

I was under the impression that it froze BEFORE trying to actual boot from HDD, but I was apparently wrong .

What capacity are each of the hard drives you tried and what are the motheboards and their installed BIOS revisions ?

Maybe the BIOSes use different sector translation schemes (wiping the partition table might be something to try) and/or the P3 BIOS can't handle drives beyond a certain capacity .

Well, the previous system was a Gateway Essential i believe. 850mhz Slot 1 Athlon cpu, AMD 756AC chipset, not sure the actual board model or bios revision, but i know board is factory to the system. The new system is a S370 PIII at 933mhz, Board is Gigabyte GA-6VXE7+ bios V4.51PG. Drives ive tested are a 60gb Samsung, which is the main boot drive, and a 120gb drive just there for storage, doesnt have an OS on it.

Reply 14 of 22, by Alistar1776

User metadata
Rank Member
Rank
Member
weedeewee wrote on 2022-12-26, 03:47:

Has that Gigabyte GA-6VXE7+ board ever been recapped ?

have no idea, i got it on ebay along with the processor and a stick of memory for 140 usd

update: formatted the 120gb drive to 32gb, installed DOS 6.22, and the system booted right to it without an issue. I get the impression the win 98 drive is corrupt, and needs a complete reinstall of the OS. However, finding a cd rom that the built in drivers in the boot floppy can support, then the system being able to find the setup files on the disk itself is proving to be a challenge.

Reply 15 of 22, by Alistar1776

User metadata
Rank Member
Rank
Member

Update: following along the idea of needing a reformat and reinstall of the OS, I set to repairing one of my older CDROM drives that I had previously deemed dead. after a grease job, and cleaning the lens with some isopropyl, I no longer had issues with getting the reinstall under way. 😁 At time of writing, the system is formatting the 60gb drive.

Reply 16 of 22, by Alistar1776

User metadata
Rank Member
Rank
Member
AppleSauce wrote on 2022-12-25, 08:22:

Hmm I've been planning on migrating from an abit bf6 to an asus p3b-f so ill keep tabs on this thread.

I figured there would be some hiccups along the way so I havent gotten around to doing it yet , im guessing uninstalling the original chipset drivers beforehand and installing the correct chipset drivers after migration might be necessary right?

Anyone else successfully pulled off what op is trying to accomplish?

End result: the best way to go about it ive found, is to do a complete reinstall of the OS. Thats what Ive done, and im currently installing drivers and such at time of writing.

Reply 17 of 22, by AppleSauce

User metadata
Rank Oldbie
Rank
Oldbie
Alistar1776 wrote on 2022-12-26, 08:23:
AppleSauce wrote on 2022-12-25, 08:22:

Hmm I've been planning on migrating from an abit bf6 to an asus p3b-f so ill keep tabs on this thread.

I figured there would be some hiccups along the way so I havent gotten around to doing it yet , im guessing uninstalling the original chipset drivers beforehand and installing the correct chipset drivers after migration might be necessary right?

Anyone else successfully pulled off what op is trying to accomplish?

End result: the best way to go about it ive found, is to do a complete reinstall of the OS. Thats what Ive done, and im currently installing drivers and such at time of writing.

Yeah I might have to as well 😒
I've got alot of stuff installed on me drive so I'm not super keen about it but if its the only option I guess I'll have to bite the bullet.

Reply 18 of 22, by Alistar1776

User metadata
Rank Member
Rank
Member
AppleSauce wrote on 2022-12-27, 05:45:

Yeah I might have to as well 😒
I've got alot of stuff installed on me drive so I'm not super keen about it but if its the only option I guess I'll have to bite the bullet.

backup the drive before doing the reinstall. everything I had on mine was either still on my main pc, or on my shelf in the form of big box pc games, so it wasnt a problem for me.

Reply 19 of 22, by AppleSauce

User metadata
Rank Oldbie
Rank
Oldbie
Alistar1776 wrote on 2022-12-27, 20:38:
AppleSauce wrote on 2022-12-27, 05:45:

Yeah I might have to as well 😒
I've got alot of stuff installed on me drive so I'm not super keen about it but if its the only option I guess I'll have to bite the bullet.

backup the drive before doing the reinstall. everything I had on mine was either still on my main pc, or on my shelf in the form of big box pc games, so it wasnt a problem for me.

Yeah I really should , I saw some ide to usb adaptors on ebay a while back, I probably should get one of those.
There's nothing mission critical on there , its just more it would be tedious to go through installing all the drivers and software again.