Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
My computer does not log into windows. I have tried all possible boot fix solutions. Currently I am in dr dos and I would like to copy the contents of my C: drive to another interal drive. Both drives are reconzable and can be viewed. Commands such as cd and dir work. However the copy and xcopy commands do not work. I have tried also possible combinations of . * \ ? and /. It says that it is an invalid command. Any information relating to this problem would be great.
I know nothing of DR-DOS, and I have never used it. However, this page tells me both copy and xcopy exist. I'd start by checking the PATH to make sure it included DR-DOS' directories, or wherever copy and xcopy are stored.
0 
When I type in xcopy /? and copy /? it gives me the commands for the copy commands. It reconizes the command however it does not execute it.
0
Well then, it should be something like:
xcopy <switches> <system drive>:\*.* <backup drive>:\But without the help, that's the best I can do.
0
C:\temp\y\incLevel>\util\xcopy /?
XCOPY R1.50 Extended file copy
Copyright (c) 1987,1988,1990,1991 Digital Research Inc. All rights reserved.XCOPY [/Help] [@][d:][path][filename[.ext]] [d:][path][filename[.ext]] [opts]
The first file specification is the drive, path and name of file(s) to be
copied (wildcard filenames allowed). This specification must be present.
Use '@' to specify that the given file contains a list of files to be copied.
The second file specification is the destination drive and path to which files
will be copied. Files will be renamed if a destination filename is specified./A only copy files with the archive attribute
/D:mm/dd/yy only copy files modified since specified date
/E allow empty subdirectories to be created
/H copy files with hidden or system attributes
/L copy the disk volume label as well as specified files
/M only copy files with the archive attribute, reset the attribute
/P prompt before copying each file
/R overwrite read-only files
/S copy files in subdirectories
/V verify that data is written correctly
/W wait for disks to be changed
=====================================
If at first you don't succeed, you're about average.M2
0
I am not sure if those methods work. I have to test them out tomorrow more in depth. By the way the make directory md and mkdir commands do not work either.
0
all possible boot solutions?
Why not use the second repair option in the original M$ installation disk to repair the boot files and restore the operating sytem.
In The Matters Of Style,
swim with the current;
in matters of principle,
Stand Like A Rock
"People demand freedom of speech to make up for the
freedom of thought which they avoid."
0
I have repaired boot files through the windows recovery console (ie. chkdsk r, chkdsk p, fixboot). None of these worked. I do not want to use the system recovery feature because it erases the harddrive and restores it back to factory presets. There is still data on the drive that I hope to recover.
0
It should look something like:
xcopy c:\*.* d:\ /e /h /s /v
If that doesn't work, then I'd say your backup drive is NTFS, and DR-DOS does not support writing to NTFS.
0
Thanks razor. How is it possible to copy the contents off of a FAT drive. Do I have to take the drive out and onto another computer and set as a slave. The problem with that is that the drive is a serial ata and all my other computers are ide. Is there any way to recover in dos.
0
You didn't say what version of DRDOS or whether there's LFN support. You did say you can 'accress' the drives.
AFAIK, COPY, MD, CD etc are all internal commands. You may have a corrupt DRDOS boot.
Note also that if your DOS does support LFNs you'll need to:
xcopy "c:\program files" p:\test
=====================================
If at first you don't succeed, you're about average.M2
0
Robert, by using the second repair feature with the original M$ installation disc, the only thing that will be lost is the updates. No personal data is lost. I have used this feature many times and never lost anything more than the updates.
In order to use chkdsk fixboot and those options you are in the first repair option mode and not the second.There is a second repair option that can be used to rep[air xp. It basically reinstalls the operating system over the existing operating system.
http://www.theeldergeek.com/repairi...
scroll down to the :
Windows Installation CD - Repair Current Installation: feature and read the directions.Quote > Note that when you perform a repair of a current installation you will be asked to enter the Product Key that came with the CD. In essence you are installing a fresh copy of XP over the existing copy. While data and settings are not destroyed, any Service Packs will have to be reinstalled after the repair process has completed. < end quote
In The Matters Of Style,
swim with the current;
in matters of principle,
Stand Like A Rock
"People demand freedom of speech to make up for the
freedom of thought which they avoid."
0
"My computer does not log into windows. I have tried all possible boot fix solutions."
- What actually happens at boot?
- Does the above include safe mode?
- Did you try safe mode w/ command prompt?
- Did you also try bootcfg /rebuild?
0
For anyone not familiar with DR-DOS, read THIS. DR-DOS used to be my favorite OS during the war days between MS DOS & DR-DOS.
I don't think DR-DOS should be run under XP at all.
i_XpUser
0
Quite agree it is like comparing a steam engine to a petrol engine, achieve the same thing but in a different manner!!!
Linux LiveCD/Boot Floppy would be a better option IMO!
0
Thanks for the responses. I am planning on trying Knoppix. It seems to be an efficient solution. The codes in Dr dos did not work. I believe there are bad sectors on the main C drive which windows is installed on.
0
You don't have to 'believe' - - that can be determined by scanning the drive. Chkdsk is on the bootable XP CD
Knoppix or Bart's PE can be used for file recovery, sure - futzing about in DR-DOS is hardly the way to proceed (as mentioned), what with all those pesky "codes" and such (heh)
"I have tried all possible boot fix solutions"
I suspect... not - it'd probably be fixed by now in that case
I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter.
0
I would like to clarify that all "possible boot fix solutions" relate to all codes suggested to be used in the Microsoft Recovery consol.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
