DEK 265 Boot Up CMOS failure EEPROM failure*

Subscribe to Thread

DEK 265LT displays CMOC is BAD: Restoring from EEPROM....... - Nov 09, 2020 by mws

Can you manually enter CMOS information in Setup and boot fr... - Nov 10, 2020 by DEKHEAD

I have been able to manually enter CMOS info in SETUP thanks... - Nov 10, 2020 by mws

Still t issue if yu remove FDD from boot sequence? ... - Nov 10, 2020 by DEKHEAD

I removed the ribbon cable from the FDD and edited the setti... - Nov 10, 2020 by mws

Assuming you have defined HDD correctly (this is a non-stand... - Nov 11, 2020 by DEKHEAD

mws

#85884

DEK 265 Boot Up CMOS failure EEPROM failure* | 9 November, 2020

DEK 265LT displays CMOC is BAD: Restoring from EEPROM.... EEPROM is BAD: No Restore was made. You MUST run SETUP followed by LOCKMOS... FAILED Any help appreciated.

reply »

DEKHEAD

#85888

DEK 265 Boot Up CMOS failure EEPROM failure* | 10 November, 2020

Can you manually enter CMOS information in Setup and boot from there?

reply »

mws

#85889

DEK 265 Boot Up CMOS failure EEPROM failure* | 10 November, 2020

I have been able to manually enter CMOS info in SETUP thanks to suggestions from this forum and get past the CMOS and EEPROM failures. Now stuck "diskette error". Any key will produce the same message. Thanks.

reply »

DEKHEAD

#85890

DEK 265 Boot Up CMOS failure EEPROM failure* | 10 November, 2020

Still t issue if yu remove FDD from boot sequence?

reply »

mws

#85891

DEK 265 Boot Up CMOS failure EEPROM failure* | 10 November, 2020

I removed the ribbon cable from the FDD and edited the setting in SETUP to "NOT Installed";. Came back with 'Diskette drive failure on drive A'. on reboot.

Still shows "Diskette error" on last line. Possible HDD issue? Thanks.

reply »

DEKHEAD

#85893

DEK 265 Boot Up CMOS failure EEPROM failure* | 11 November, 2020

Assuming you have defined HDD correctly (this is a non-standard CMOS setting), unless it is a totally dead HDD not the normal error for HDD failure. More inclined to think a CPU issue, I have not seen a "bad EEPROM" on that machine before... but presumably that migh not be detected until it is needed. Please contact me offline. DEKHEAD@att.net

reply »