Windows 95/98/Me/NTPost your Windows 95 / 98 / ME and NT questions here. Please make sure you specify your OS version.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
No luck. When I dropped the H and ran the command it said "invalid switch -k . So I dropped the H & K next time and it said invalid switch -C. I figure it would "invalid switch" me to death so I just decided to post what has happened so far. ONE thing though in your command is there a space between the second X and the D? I've been putting a space there instead of running the command as one whole string.
Those are not X's. They are asterisks, the little star shaped symbol on the key for the number eight. You are correct. There is a space after the second asterisk.
It is c/colon/backslash/asterisk/period/asterisk/space/d/colon/backslash/forwardslash/s...and so on.
xcopy c:\*.* d:\/s/e/h/k/c/l/r
Try the command again exactly as written above, with asterisks instead of X's.
I should have asked you at the beginning to tell me something about your Crutchfield computer. Desktop or laptop? What processor? How much RAM?
Are you still having fun? Do you want to keep going?
I'm sorry, I meant asterisk. Yes, I'm still having fun and I want to keep going. The Crutchfield is a tower with a Symphony G486SLC motherboard with a 486 DX33 CPU a math co processor 4 megs of ram (but I found 4 30 pin 4 meg strips to add for a whopping 20 megs) a Video 7 1 meg video card a 5 1/4 floppy drive a 3 1/2 floppy drive a Texel 1X CDrom a sound card (unsure of brand) matching black 13"? monitor and keyboard; mouse is a serial port type. And like I said from the start I got this from a cousin of mine that ordered it new in 1994. It has all the books and paper work except for the bill of sale which IIRC was $1800. The DOS, Windows 3.1 and Video 7 software are on 5 1/4 floppies and the Texel sound card and CDrom drivers are on 3 1/2 floppies.
Size of the old hard drive?
Size of the new hard drive?
Number of ISA slots?
Number of PCI slots?
Did you rerun the XCOPY command? What happened?
Are you booting from the old drive, and does Win 3.1 load and run successfully from there?
If yes, do the video, mouse, CD-ROM and sound all work OK?
Does the new drive show up OK as a second, or slave drive? Can you browse, copy, change, add and delete files with Program Manager?
When you installed Windows 3.1 on the new hard drive, did you choose Express Setup or Custom Setup?
What was your choice for video driver?
Have you considered running the computer with two drives? Boot from C and install your apps on D?
Have you considered deleting enough files to make room for your HP Apollo printer software on the old drive?
The reason I ask these questions is that it may help to work with DOS and 3.1 on a running computer for a while until your former familiarity with all the commands is reestablished. You can review the files which Microsoft provides (and which Crutchfield may have enhanced) to explain the setup process, and, when you are ready, copy the environment files over to the new drive and put them in the right locations.
Last, do you have a DOS 6.0 book or manual? How about a book or manual for Windows 3.1?
The answers to the questions will help me to understand the situation and come up with better ideas for how to get you where you want to go. Wasn't that was Bill Gates theme for Windows 95? Where do you want to go today?
It seems to me that you have the best situation right now, running two drives.
I don't understand what's filling up your 200 MB hard disk. A 486 machine running Windows 3.1 often shipped with a 40MB HD. If you install your apps on the slave and save your files there, you should be able to defrag the 200MB drive and improve performance by putting the swap file on the second drive.
Before Wordpad, there was a word processing program called Windows Write that saved its files with the .WRI extension. In Program Manager, in the Accessories Group, you will see an Icon labelled Write. That opens the program. However, if you double click on the file, e.g. readme.wri, the Write program will open and display the file. The files I listed should all be in the C:\Windows directory.
My suggestion is that you read those .WRI files, also look for and read the .TXT files, especially SETUP.TXT
Then hit those books of yours and learn to use Windows 3.1 while you have it running. Make a bootable rescue diskette and save the key environment files like AUTOEXEC.BAT, CONFIG.SYS, SYSTEM.INI and WIN.INI to a diskette so that you will have a back-up copy. Don't try to install Windows again until you feel you thoroughly understand how those environment files work and the choices you will face in SETUP.
Get your Apollo printer installed on the slave drive and print out a Microsoft System Diagnostics (MSD) report.
Learn to use the Microsoft Backup program and save a backup of the master hard drive to the slave.
Then, if you decide you want to try reinstalling Windows 3.1, next time choose the CUSTOM option. That is where you get to tell Windows exactly what driver to use, instead of relying on the detection process.
There is a specific choice for the Logitech mouse (you did read that Microsoft Knowledge Base article, right?) which will install LMOUSE.COM and there is a choice in each section to ignore all the Microsoft drivers and instead "require a manufacturer's disk." That's where you insert your floppies and install the drivers furnished by Crutchfield.
You have all the materials you need. The only task remaining is to learn to use them.
The one knotty problem is the real time clock. There is a battery inside the little black Dallas module. You might try leaving the computer running for 24 hours and see if it picks up a charge. My experience buying replacements is poor. It's always old stock and the replacements don't work. Whether in the computer or on the shelf, they are obsolete. It's possible you could find an old IBM XT vintage ISA add in AST memory board with a clock module on it. Those had replaceable coin type batteries. If you find a board it's worthless if it doesn't come with drivers and programs diskette.
That's about all I have to offer. I leave you with two bits of wisdom:
"You have to study a great deal to learn a little" (Montesquieu)
"That which we do not understand we do not possess" (Goethe)
You know, I have no idea why I didn't think to just slave the 600MB. Oh that's right I didn't know as to whether the CDrom would cause problems being connected. Like I said earlier I really don't know much about SCSI. Although I should've thought something since the SCSI board is part of the sound card.
Yeah, I'll hit those books. Kinda strange tho, I never picked up and read anything pertaining to an operating system. Just taught myself. Gettin' old. And of course I have this topic to review for good reference.
As for the battery it is stone cold dead. I left the machine running for 2 days early on and no luck. BUT, I was scrounging around my storage area and found another RTC that holds a charge. First to say what I have in my tower is a Twin Head RTC TH1287. The other RTC is a Twin Head, also. But the number is TH6887A. I did some Googling on these and found a web site called www.resource800.com . On their main page they list Dallas RTC's and mention basically what they are the same as. Well I learned that there is a difference between the TH1287 and TH126887A. The "A" means it has a CMOS reset capability. Which is where I have a problem. When I installed that RTC in my Crutchfield and went to CMOS the time and date were right (scary since that tower hasn't been turned on in about 3 years, and that was only for about 2 hours), but the Type 47 hard drive (C) was different, nothing for "D" drive and "A" drive was for a 3 1/2 floppy instead of the 5 1/4 floppy that is my "A"; and nothing for "B". So, I put in all the right info saved it and when it was booting it just hung up. As for taking the RTC apart I am not sure about the 2 Twin Heads, if it can be done they are pretty tight. I also have a socket 7 board with a Houston Tech RTC but it has a HT12888A but it has more pins that the 2 Twin Heads. But it did come apart and I see it has a button battery soldered on it. Comparing the HT with the TW's it looks like the TW's are glued. So it might be harder to separate. I thought of snipping some pins off the HT but I have the problem of it being an "A" series. If I can figure out how to get an "A" serise to work in my tower I'll be in business.
Thanks for all your help. I will let you know somehow my progress.
Thank you. I know when I see an old computer at a thrift store I just want to buy it. Like today, I seen an old AST with Win 3.1. Complete $20.00; it was tempting. But no, I gotta have fun with the one I have.
Speaking of which I kept getting the BSOD and cured the problem by removing the 600 meg slave drive. As for why it caused that I am not real sure. But last night while I was trying to research the Real Time Clock batteries I read this long FAQ and it was mentioned that like in my case of having 2 hard drives a CDrom drive a 5 1/4 drive and a 3 1/2 drive I should be running a 300 watt power supply. I only have a 250 watt. Not sure if that is right but for whatever reason it is back to normal. I have wondered too if it is possible that because I have a dead RTC that it might be causing some of my grief? From what I think it does more than keep the clock and the rest of the CMOS right.
That is where we were at. I was going to use the 600 meg as a slave but by having it slaved it caused the blue screen of death on any program I tried to launch, whether it was from a floppy or CDrom or the master hdd. I am think also that maybe I can't run the SCSI CDrom and the 600meg hdd. Even though the 600 went to "E" this old computer might not like it.