I put in a 'new' SS7 mobo in my wife's solitaire machine and pretty much had an uneventful installation of Win2K as well as the sound/vid/HPNA/modem cards. The rig works great except for this nagging thing on cold boots.
Only thing that bugs me now is this "CMOS checksum error" everytime I cold boot. The PC still boots fine but either I go back in and correct the CMOS date (everything else is on 'auto') and double check all other BIOS info or just plain hit F1 to continue booting (wrong date once Win2K is up and running). It seems that the BIOS goes back to where it 'was' before I installed it.
This phenomenon does not happen on warm boots. I also cleared the CMOS via the CMOS clear jumper. I have not checked the CMOS battery - could this be the culprit or is there somethine else I should check?
The mobo is a Jetway 542B(?) with the Via MVP3 chipset. CPU is a K6-2 500, 128 MB PC100 SDRAM, Vortex2 soundcard, 32MB Radeon 7200 AGP vid card, Diamond HPNA nic, USRobotics 56K ISA modem.
Any assistance will be greatly appreciated.
Only thing that bugs me now is this "CMOS checksum error" everytime I cold boot. The PC still boots fine but either I go back in and correct the CMOS date (everything else is on 'auto') and double check all other BIOS info or just plain hit F1 to continue booting (wrong date once Win2K is up and running). It seems that the BIOS goes back to where it 'was' before I installed it.
This phenomenon does not happen on warm boots. I also cleared the CMOS via the CMOS clear jumper. I have not checked the CMOS battery - could this be the culprit or is there somethine else I should check?
The mobo is a Jetway 542B(?) with the Via MVP3 chipset. CPU is a K6-2 500, 128 MB PC100 SDRAM, Vortex2 soundcard, 32MB Radeon 7200 AGP vid card, Diamond HPNA nic, USRobotics 56K ISA modem.
Any assistance will be greatly appreciated.
Facebook
Twitter