FORMAT C: (does not work)...

[jdc2000]

If you can boot from your floppy, and you have a newly formatted C: drive, type the following from the A: prompt:

SYS C:

Or, if you are re-formatting the C: drive, type: FORMAT C: /S

Either of these commands will put the system on the hard drive so you can boot to C: (You will still not have Windows on the C: drive, but you can then install a CD-ROM driver that I will e-mail you.)

[jdc2000]

If you send me your e-mail address, I'll send you a program that will install a generic IDE CD-ROM driver for you automatically.

[cyndy10]

OK, I have the contents of the floppy on C: drive. The screen, when I try to boot says this:

The diagnostic tools were successfully loaded to Drice D.

MSCDEX version 2.25
Then some Microsoft version info..
DRIVE E: = MSCD0001 unit 0

To get help type help and press enter.

Anyway, does that help with the CD-ROM driver info? I have E: drive, but it just won't go.

My email addy is:
[email protected]

Tell me when to check it...

AND THANK YOU. I have a newly formatted floppy for it.

I want to partition this drive but I have never FDISK'ed before, I read back and found this: http://personal.picusnet.com/jtmurphy/fdisk.htm and this: http://support.microsoft.com/default...;EN-US;q255867

The drive is 43.116Gigs, what sizes of partitions would you recommend? I'll format it again after that, but if I pertition the drive maybe I could avoid a major pain the next time.


------------------
1) AMD Athlon K7 1.2Ghz, 320Ram, onboard Audio and Video.
2) AMD K6/2 550Mhz, 194RAM, Monster Fusion, and ? Sound...
3) Linksys router and cable.

[This message has been edited by cyndy10 (edited 12-01-2001).]

[jdc2000]

I have sent you the files for a generic DOS IDE CD-ROM driver, however, if your current boot disk is showing that MSCDEX loads correctly, but you can't do a 'DIR E:' successfully, you may have a bad CD-ROM drive. If you were able to get the system files installed onto your C: drive, you should now be able to boot without a boot diskette to a C:> prompt. If you can, try installing the CD-ROM driver I sent you, then re-booting. If you get successful messages about the Samsung driver and MSCDEX loading OK, but you still can't get the CD-ROM drive to access any CD's, it may be time to try another CD-ROM drive.

[jtdoom]

jeesh...

CMOS lost its settings?
loose cables?
windows 3.1?
DOS (which version?)
(for this disk, you need fat 32 support.
win3.1 does not have fat 32 support.

an old norton disk? (for these drives, you need version four or up)

at least you are not afraid of getting in there, and you seem to know how a command line works.

in my way of thinking, in your working machine, you should boot off the cdrom to create a floppy.
(yes, that works too.)

you should do fdisk /mbr
(I suspect some nasty is still in there)

you should maybe also get CIH kill at symantec.

and above all, you should read a few relevant things in "butter".
(yes, it also has links to picusnet and microsoft, and it explains oodles of things you probably don't really need, but should be aware of...) http://discussions.virtualdr.com/For...ML/038724.html


------------------
I think we forgot...

Kind regards, Jaak

[cyndy10]

1) CMOS lost its settings?
I have everything set to the defaults as of now.

2) loose cables?
Not a chance, checked that a dozen times.

3) windows 3.1?
*blush* - Yup, I'm desperate, had to try it.

4) DOS (which version?)
I dunno, but the computer was new in April 2001

5) (for this disk, you need fat 32 support.
win3.1 does not have fat 32 support.
*another blush* I KNEW THAT, but it slipped my mind... I also suspected the DOS would be incompatible, but hey, a girl's gotta try...

6) an old norton disk? (for these drives, you need version four or up)
It was Norton AV 2002, brand new trial

7) at least you are not afraid of getting in there, and you seem to know how a command line works.
LEARNED BY NECESITY, not a bit timid at the command line, it doesn't bite. When you are in the middle of an Internet game of WHOOP ASS with several hackers, well, you learn quick. START | RUN | ...command / and I are old friends now.

8) in my way of thinking, in your working machine, you should boot off the cdrom to create a floppy.
(yes, that works too.)
Should I switch it in CMOSS? Explain the process, never done it and want to be sure I understand exactly what you mean.

9) you should do fdisk /mbr
(I suspect some nasty is still in there)
SO DO I. That is a neat command - I looked it up, great idea. I also thought about the FORMAT C: /U command. Thoughts?

10) you should maybe also get CIH kill at symantec.
Never heard of it, but CIH sounds like a nasty bug to me. I'm on the way to symantec.

Thanks, I'll be right back.


------------------
1) AMD Athlon K7 1.2Ghz, 320Ram, onboard Audio and Video.
2) AMD K6/2 550Mhz, 194RAM, Monster Fusion, and ? Sound...
3) Linksys router and cable.

[cyndy10]

The CIH_Kill tool only works from DOS WITHIN WINDOWS, so I am getting something called F-Prot that will do the trick. I'll report back. I'm making the Sscdrom disk now and I'll report back soon. I think I am going to redo the MBR and use the F-Prot DOS AV tool first though...

------------------
1) AMD Athlon K7 1.2Ghz, 320Ram, onboard Audio and Video.
2) AMD K6/2 550Mhz, 194RAM, Monster Fusion, and ? Sound...
3) Linksys router and cable.

[cyndy10]

I NEED TO COOK DINNER, GIVE ME 1 HOUR OR SO....

------------------
1) AMD Athlon K7 1.2Ghz, 320Ram, onboard Audio and Video.
2) AMD K6/2 550Mhz, 194RAM, Monster Fusion, and ? Sound...
3) Linksys router and cable.

[gnh]

Cyndy consider installing the current hard drive from the down machine in the working computer as a slave. (set jumpers and reset when done) Then copying the windows cab files to that drive. Reinstall the hardrive in the non working computer and install windows from there.

Another option is to copy the complete "C" drive from the working computer to the slave drive. Most drive manufactures have utilities that do that easily. Some recommend deleting the compete Enum key from the registry and let windows find the correct hardware when it boots. I have never tried it but it should work.

This will also bump this back to the top.

------------------
gary
------------------
No question is hard if you know the answer.

[jtdoom]

I think you probably read the "how to"
in that long post I linked to.

duh, I forgot about that windows bit for CIHkill.

anyway, if a scan from a known clean recent AV rescue set from NAV 2002 did not find it, it wasn't there?

I trust you'll be up and running soon.
a while ago we had a very very long thread about security related matters
much of it is still relevant.

this was a summary http://discussions.virtualdr.com/For...ML/041590.html



------------------
I think we forgot...

Kind regards, Jaak