• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Ysing copy with wildcards (*.*) in WinXP Recovery Console

P

prowsej

Member
By default the Windows XP Recovery Console does not allow wildcards to be used with the copy command (why!?!)
I need to use wildcards to copy a large number of files. How can I do so? It doesn't appear that I can run a program like xcopy.exe to bypass the Recovery Console. Suggestions?
 
The Recovery Console is extra crippled to be annoying and make it nearly useless, I would suggest booting another OS and copying the files from there.
 
Originally posted by: Nothinman
The Recovery Console is extra crippled to be annoying and make it nearly useless, I would suggest booting another OS and copying the files from there.
Click to expand...

This is not so.

The Recovery Console is actually a wrapper around textmode setup; it's not cmd.exe at all. Though the command syntax is largely the same as DOS commands, it's an entirely different command interpreter. The machine is basically running textmode setup at this point in time and is quite limited as a result of that, not as a deliberate decision to cripple the console.

And you're right: it doesn't support wildcards. Period.

And you can't run programs from recovery console. All the commands are built in to the console command interpreter, and that's all you've got access to. (Not even a text editor there.)
 
What OS would you suggest that can either be booted from a floppy or a CDROM and can access both FAT32 and NTFS file systems?
 
If you're copying the data from NTFS to a FAT drive then either Linux or DOS (with NTFSDOS) would work fine. If you need to do any writing to the NTFS partition then DOS (with NTFSDOS Pro) is pretty much necessary, unless you want to do a paralell install of XP to move the data around in that.
 
NTFSDOS Pro, eh? Sounds cool. I'll check that one out.

Microsoft should really continue to support DOS since they never created a replacement OS that's bootable from write-only media ...
 
Microsoft should really continue to support DOS since they never created a replacement OS that's bootable from write-only media ...
Click to expand...

DOS sucks and should be dropped, but they should atleast provide a semi-decent recovery console.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top