Cmos

Hi folks

Can anybody tell me how to read and to save my CMOS settings short of opening them one at a time on reboot, and writing them down long hand?

I used to have a small program that would do this and save the setting to a floppy disk file but I've lost it and cannot find a replacement save some huge systems data programs that one needs to purchase. I don't want to buy such software just for this one simple task.

I realize that a boot disk saves the info but is it saved in Windows or the root drive? If so, what's the file name?

Thanks all

 

I use cmosram2 for that job. It's shareware with no time out. Costs $5 to register. I also have one called cmos.com but I forget where it came from. It's a single .com file that stores the setting within itself whereas the cmosram2 has four files that are needed for it's magic. Either way of course, keep them on all your start-up disks and make extra copies unless you don't plan to write those babies down (only safe way).

HTH

ps, As far as I have ever seen, no cmos storing software stores ALL the nuances of the settings, only the principal ones, mainly the drive geometry. That way you can get recognized and booted. I wish I could find one that does a complete job but I suppose it would have to be BIOS specific and would take several versions to cover all.

 

Thank you Zepher.That CMOS.com sounds like the old program I used. I'm assuming this is OK to use with Win 98.

Just wondering, since you said something about an `old system'.

 

Yeah, they all work in dos, so the only problem might be when you hit Windows 2000 or XP you might need a dos boot disk. Other than that they're carte blanche and await your pleasure.

I managed to locate cmos.com for you at This site and you'll find several other of the same ilk there. It's the last one listed on that page. You may want to try some others as well.

Also be advised that there is a virus called cmos.com of all things but it does it's dirty work by placing itself in the Windows directory. I mention this for no important reason other than if you want to keep the cmos.com on your hard drive also, you should possibly keep it on the root to prevent it being overwritten if you did happen to get that virus. Of course, on your start-up floppies is where it would do the most good.

FYI, If you have an older printer that supports DOS printing, I would recommend displaying all the cmos settings and hitting "Print Screen" so as to get a hard copy of them. That failing, the paper and pencil have a lot going for them.

Regards

 

Once again, thanks Zephyr. I DL's CMOS.com in the form of cmos_sah.zip. Don't know if my printer supports DOS or not. Will have to check. It's a Lexmark Z51.

Will let you know. Thanks, too, for the tip re the virus.

I can make a reboot disk for Windows but have been relying on my set of Norton start up disks. Suppose I ought to have both.

Take care.

 

Also, if you use Norton Antivirus, it is backed up when you create the rescue disks. Put the first disk in and boot from it and you will have an option to restore your cmos.

 

MORE CMOS

Hi again Zephyr

I did as instructed including making a Windows boot disk with the CMOSRAM file added and while I'm not surprised, when the computer reboots, I receive a `too many parameters' message re CMOSRAM2; and a `Bad Command' message re CHKCMOS2.

Loading isn't affected but can I modify the Autoexec.bat file to prevent these messages?

And to Zander, thank you. I never realised that the Norton Rescue Disks would back up the CMOS but it certainly makes perfect sense.

This all started from a desire to not only back up the CMOS but also to find a program that would provide a `text' readable result [and not a row of numbers meaningless to me].

Thanks to both of you.

 

I never realised that the Norton Rescue Disks would back up the CMOS but it certainly makes perfect sense.

If you do make the NAV rescue disks and then make ANY permanent changes to the system MAKE NEW rescue disks also

The same applies to any software that backs up the CMOS.

If you make permanent changes to the CMOS settings in order to make things work better and do not make new rescue disk and use the old ones you will destory all changes you have made.

Also to keep them current they should be updated after updating NAV.

BillyBob

 

Welt,

I don't know why you would be getting those errors unless you placed something in the autoexec.bat calling the cmos program you downloaded.

I don't recommend using it that way. Just place the program on one of your normal Windows start-up disks and run it manually from a DOS A:\ prompt when you boot to that disk. That way it will retain the settings for your use later. Rerun it when you change drive configurations.

I'm not sure how you got directed to place a call in the autoexec.bat file but that was a bum steer.

Edit, I reviewed the readme file with cmosram2 and I see where they have outlined how to place their program in the Autoexec.bat file so I now know what you are referring to. I think I must have considered that when I first started using the program but decided it wasn't necessary to run it with every boot. Often times software people get the idea that their stuff is so important as to warrant that. I usually opt out but you decide what works for you.

Here's exactly what I did. Copy the four file of the program to a directory named CMOSRAM2 and place that directory on all of your startup disks. Place another copy on your C: root. Now run the program in Windows by going to that folder and double clicking cmosram2.exe that will give you the menu. Select to store the cmos settings and exit the program. Then double click on chkcmos2.exe and it should tell you that the setting haven't changed. Music is included, that's what the cmos.ram file does. The remaining file is the cmosram2.doc which contains all the gory details of the program.

Now, boot up to the startup disk you put this folder on and run each of the commands again. eg, From an A:\ prompt type A:\cmosram2\cmosram2.exe and press enter. Then go through then menu as before and elect to store the settings. The type a:\cmosram2\chkcmos2.exe and it will report no change hopefully. That's all there is to it. You can explore the other features about setting the system clock but I never messed with that.

Do all that each time you change the drive layout and you'll always be ready. Of course if you have the Norton disks you're more than ready, kinda like belt 'n suspenders. Then go write it all down too!!

 

AUTOEXEC.BAT

Hi Zephyr

At the risk of being cited for copyright infringement for which there is no such intent, I have extracted this instruction from CMOSRAM2.DOC file:

Quote: " However, one problem with a program like CMOSRAM2 is that it's easy to use it and forget about it. After all, it could be several years until you need it. In that time, you could easily change your hardware and forget to update CMOS.RAM, defeating the program's purpose and increasing your hassles.

Enter CHKCMOS2. Just install this program in your AUTOEXEC.BAT file along with a copy of CMOS.RAM in the same directory. This is done as follows:

1. Create a directory called CMOSRAM2. (MD CMOSRAM2)
2. Copy the files CMOSRAM2.EXE and CHKCMOS2.EXE to this directory.
3. Run CMOSRAM2 as outlined for the disaster disk, and use option 2 to save the CMOS contents to a file.
4. Add the following lines to your AUTOEXEC.BAT file using DOS EDIT:

CD\CMOSRAM2
CHKCMOS2
CD\

Don't bother to add CMOSRAM2 to your PATH statement. There's no need to use up precious space in your path, which is limited to 127 characters." Unquote.

There you have it. I can just as easily remove it. Given my age and my memory, the CMOS could be changed by a technician and I'd never think to rerun CMOSRAM2. Latter is why I went this way.

 

4. Add the following lines to your AUTOEXEC.BAT file using DOS EDIT:

CD\CMOSRAM2
CHKCMOS2
CD\

Just as a little suggestion in hopes you do not get any surprises later.

Don't try the above with Win98 ME. ME will toss it out so fast you will think it was never there.

ME will not except DOS Commands in the Autoexec.bat.

I can vouch 100% for that. ME would not allow me to run NAV boot check or another DOS .bat file I had in the Autoexec.bat.

ME also will not allow 16bit DOS drivers to be loaded from the Config.sys

That is one of several reason ME left and FE came back.

BillyBob

 

OOPS SORRY

Sorry Billy Bob,

I missed your earlier post. I redo my Norton Rescue disks regularly and if there's an update other than virus files, I then update the disks. I presume any change to the CMOS would automatically be caught in the update. I do NOT make all new disks.

Re the second, the Autoexec.bat info you posted is
precisely what I posted earlier and what I was talking about. I don't understand Win 98 ME. They are two different OSs. I run Win 98 SE and the change in the Autoexec.bat file does not seem to have had any alterior effect.

I have no plans to go to either ME or XP.

Thanks for the responses.

 

Welt, If you want to use it that way, I think I see what the problem might be. Edit your autoexec.bat and add a space between the Cd and the rest of the command line (two places)so instead of reading:

CD\CMOSRAM2
CHKCMOS2
CD\

It says:

CD \CMOSRAM2
CHKCMOS2
CD \

I think that'll get you back on track. Your problem is you followed the directions to the last detail, even including the authors typographical error. I ran across another error in that same readme file, his site address was listed with \\ instead of // and it caused me to paste his site link improperly at first try here. Fortunately the program works better than the documentation.

 

Welt []

I redo my Norton Rescue disks regularly

I am gald to read that.

I don't understand Win 98 ME.

That makes two of us

They are two different OSs.

That is for sure.

I run Win 98 SE and the change in the Autoexec.bat file does not seem to have had any alterior effect.

SE is the last version of 98 to allow DOS commands in the Autoexec. And as long as the syntax is correct it should not have.

I have no plans to go to either ME or XP.

That makes two of us there also. IN fact I have to reason to go any higher then FE. Mostly because we have quite a bit of DOS software and FE handles it very nicely.

Thanks for the responses.

You are welcome.

I do feel more relaxed now that I know you are aware of the necessity for and do renew your rescue disks.

BillyBob