Jump to content
IGNORED

Computer won't even boot to bios!


Recommended Posts

There’s still many unknowns, like trace damage, and voltage levels/quality. And other stuff. Trace damage can really be tiny and underneath other parts. But you have to look for telltales.

 

If you’re going to build one up, just get all industry standard form factors and parts.

 

If you think you’re gonna continue trying with this machine I’ll see about finding gateway manual for it.

 

Edited by Keatah
Link to comment
Share on other sites

10 minutes ago, Keatah said:

There’s still many unknowns, like trace damage, and voltage levels/quality. And other stuff. Trace damage can really be tiny and underneath other parts. But you have to look for telltales.

 

If you’re going to build one up, just get all industry standard form factors and parts.

 

If you think you’re gonna continue trying with this machine I’ll see about finding gateway manual for it.

 

I'm not sure I'll do either. I just wish I had another machine that had ISA... 

Link to comment
Share on other sites

What disk type is configured? 

 

A board this old may suffer from the "No LBA, no ECHS" problem.  If so, the BIOS only responds to a fixed list of hard-set hard drive size types.

https://vintage-pc.tripod.com/types.html

 

The solution to that, is to set up a DDO, such as DiskManager or E-Z bios.

 

https://www.philscomputerlab.com/ontrack-disk-manager.html

https://www.philscomputerlab.com/western-digital.html

 

Those both consume a small chunk of low dos memory to install a software defined INT13 handling routine which is able to do LBA and ECHS translation modes.  All they need to be able to function, is for the drive to have an addressable boot sector. As such, the BIOS defined type can be very much "not correct", as long as the drive responds reliably, and starts trying to boot.  The DDO takes over, then hides the real boot sector, and chain-loads a second one in the next logical sector down, which it then presents as the first logical one, using its handler routine.

 

Linux does not need a DDO, because its launcher starts from the boot sector, loads a small Initial ramdisk with disk controller drivers, and then immediately goes into 32bit disk driver mode, which does not use INT13 at all.

 

  • Like 1
Link to comment
Share on other sites

I decided to put the original HDD back in the computer as I'm going to put Window 3.1 on it instead. I'm now focused on upgrading the machine with a better cpu and sound card (it currently has an AdLib). Thanks for all your help! :) 

Edited by RetroB1977
Link to comment
Share on other sites

If you should somehow never figure out how to get into the cmos setup, you could also use gsetup, or similar on it.

 

https://archive.org/details/systemutilities

 

It was not altogether uncommon to "not provide an actual ROM setup program", and instead, use a special partition on the disk drive for that. ROM chips were expensive.

 

Since this a a phoenix bios, I would use either the generic phoenix setup program in that package, or use gsetup on it.

 

 

 

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...