1. Scandisk Windows 10
2. Dos Exe Format
3. Download Xcopy.exe For Dos

I am running windows 98 original. I started the day with a normal boot into windows which gave me an error 'error loading gdi.exe', then a screen that. Uses normal DOS interface instead of Windows 95 graphical. The Dos version of Scandisk does not want to run while Win95 is. Scandisk.exe: c: windows command: 7.0.

When I run following code for defragment using batch file under XP window SP3, it takes only a few minute and get it done, but when I use window's defragment tools, it takes at least 30 minutes, will Window's defragment tools be better than following coding? Does anyone have any suggestions on how to code the batch file to perform defragment like window does? @echo off echo Y C: WINDOWS system32 chkdsk.exe /F D: C: WINDOWS system32 defrag.exe d: -F On the other hands, when I run following code, I get the same issue as defragment does, it only checks for a few minute, but when I run window's Scandisk, which require restart window XP, and take 1 hour to complete scan, will Window's Scandisk tools be better than following coding? Does anyone have any suggestions on how to code the batch file to perform Scandisk like window does? Echo y chkdsk D: /F Thanks in advance for any suggestions Thanks in advance for any suggestions. To get such outstanding performance you may need to look into the new Commodore 64. Sorry - I was making a dumb joke beecause you keep saying ScanDisk which is a very old DOS command from more that 10 years ago.

Scandisk Windows 10

You mean ChkDsk. YOu cannot runChkDsk on a mounted drive that is in use - as has been pointed out by AbqBill - with the /F argument It will just schedule the ChkDsk for the next reboot. Defrag will run fast if it has already been run. Subsequent runs may take only a few seconds. The GUI always takes a litle longer. This is how it works. You cannot change that.

Dos Exe Format

There is basically no difference between the commandline and the GUI. To get such outstanding performance you may need to look into the new Commodore 64. Sorry - I was making a dumb joke beecause you keep saying ScanDisk which is a very old DOS command from more that 10 years ago. You mean ChkDsk. YOu cannot runChkDsk on a mounted drive that is in use - as has been pointed out by AbqBill - with the /F argument It will just schedule the ChkDsk for the next reboot. Defrag will run fast if it has already been run.

Subsequent runs may take only a few seconds. The GUI always takes a litle longer. This is how it works.

You cannot change that. There is basically no difference between the commandline and the GUI. Defrag will run fast if it has already been run. Subsequent runs may take only a few seconds. The GUI always takes a litle longer.

This is how it works. You cannot change that. There is basically no difference between the commandline and the GUI. Jv After I run Chkdsk under window, it will restart and run on text screen with blue backgound, which show many command line, but it takes more than 30 minutes. On the other hands, when I run batch file with following code, it only takes less than 10 minutes, the difference in period is a lot, do you confirm that the task using batch file on following code is the same as the task running chkdsk under window and require restart window on processing chkdsk? Does anyone have any suggestions?

Echo y chkdsk D: /F Thanks in advance for any suggestions.

Dos Utilities: Scandisk Scandisk Runs the ScanDisk disk-repair program. Syntax To check and repair the current drive: SCANDISK To check and repair a drive: SCANDISK drive: /ALL /CHECKONLY /AUTOFIX /NOSAVE /SURFACE To check and repair an unmounted DriveSpace compressed volume file: SCANDISK drive: DRVSPACE. Nnn /CHECKONLY /AUTOFIX/NOSAVE To examine a file for fragmentation: SCANDISK /FRAGMENT drive: filename To undo repairs you made previously, use the following syntax: SCANDISK /UNDO undodrive: /ALL Checks and repairs all local drives. /AUTOFIX Fixes damage without prompting. /CHECKONLY Checks a drive, but does not repair any damage. /CUSTOM Configures and runs ScanDisk according to SCANDISK.INI settings.

/NOSAVE With /AUTOFIX, deletes lost clusters rather than saving as files. /NOSUMMARY With /CHECKONLY or /AUTOFIX, prevents ScanDisk from stopping at summary screens /SURFACE Performs a surface scan after other checks. /MONO Configures ScanDisk for use with a monochrome display. Drive The drive to be worked on (Default is the current drive) undodrive The drive containing the Undo disk. /CLIP Shortens long file names to regular 8.3 format. (?) /HELP Same as /?

/MOUNT Mounts DriveSpace volume. Same as using 'Mount=Always' in SCANDISK.INI /NEW? /NOLOST No prompt for surface scan, no check for lost clusters. /NOUI Uses normal DOS interface instead of Windows 95 graphical interface. /TEXT Same as /NOUI. (?) /TIME During surface scan, marks sectors that take longer than usual to read. These sectors may be on their way to failing totally.

Download Xcopy.exe For Dos

Same as using 'ScanTimeOut=On' in SCANDISK.INI. Note. The Dos version of Scandisk does not want to run while Win95 is running. Rather than signalling an error, it automatically transfers control to the Windows version of Scandisk. File Details File Name Default Location Dos Ver. Size Date Source Scandisk.exe c: windows command 7.0 Win95 134 738 11/07/95 Win95 7.1 Win95 (OSR2.x) 142 353 24/08/96? Win98 143 818 1 11/05/98 win9842.cab Win98 SE 143 818 1 23/04/99 win9846.cab Superscripts denote which same size files, if any, are identical (using ).

If you should have any comments or suggestions, please contact:. This page last revised: August 29, 2000.