[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Single Page
Top Document: comp.os.msdos.programmer FAQ part 4/5
Previous Document: - How can I access a specific address in the PC's memory?
Next Document: - How can I access memory beyond 640K?
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Single Page
Top Document: comp.os.msdos.programmer FAQ part 4/5
Previous Document:
Next Document:
- How can I read or write my PC's CMOS memory?
There are a great many public-domain utilities that do this. The following files can be downloaded from <http://www.simtel.net/pub/msdos/sysutl/>: cmos14.zip 5965 920817 Saves/restores CMOS to/from file cmoser11.zip 28323 910721 386/286 enhanced CMOS setup program cmosram.zip 76096 920214 Save AT/386/486 CMOS data to file and restore rom2.zip 15692 900131 Save AT and 386 CMOS data to file and restore setup21.zip 18172 880613 Setup program which modifies CMOS RAM viewcmos.zip 11068 900225 Display contents of AT CMOS RAM, w/C source A program to check and display CMOS memory (but not write to it) is downloadable as part of: <http://www.simtel.net/pub/pd/50522.html> <ftp://garbo.uwasa.fi/pc/ts/tsutle23.zip> Good reports of CMOS299.ZIP have been posted, but it no longer appears to be online. Stan Brown, the former list maintainer, reports that he personally tested CMOSRAM and that it worked fine. It contains an excellent (and witty) .DOC file that explains the hardware involved and gives specific recommendations for preventing disaster or recovering from it. It's $5 shareware. Robert Jourdain's {Programmer's Problem Solver for the IBM PC, XT, and AT} has code for accessing the CMOS RAM, according to an article posted in this newsgroup.
Top Document: comp.os.msdos.programmer FAQ part 4/5
Previous Document:
Next Document:
Part1 - Part2 - Part3 - Part4 - Part5 - Single Page
[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
jeffrey@carlyle.org (Jeffrey Carlyle)
Last Update October 22 2009 @ 05:28 AM