Hi Per,
Your best bet is to post here...
microsoft.public.win2000.cmdprompt.admin
Lots of batch file experts there.
Some of this is beyond me, but here is what I do know.
@echo off
break off
[[C:\>break /?
Sets or Clears Extended CTRL+C checking on DOS system
This is present for Compatibility with DOS systems. It has no effect
under Windows XP.
If Command Extensions are enabled, and running on the Windows XP
platform, then the BREAK command will enter a hard coded breakpoint
if being debugged by a debugger.]]
start ********************** START script begins ************************ @echo off
The following two lines previously inserted to try to overcome my problems:
cd \windows\prefetch
del ntvdm.*
Get rid of the above line. Simple explanation: the listing for ntvdm.exe in
prefetch only shows that ntvdm.exe has run at some point. Better
explanation below for prefetch.
ntvdm.exe and wowexec.exe run every time a 16-bit program runs. SWAG:
epurwp.exe, strus.exe and report.exe are 16-bit.
If command.com ever runs then ntvdm.exe will run.
Try this.
Open command.com...
Start | Run | Type: command | Click OK |
Open the Task Manager, Ctrl + Shift + Esc | Click the Applications tab |
Right click MS-DOS Prompt | Select: Go To Process |
The Processes tab will open with ntvdm.exe highlighted
wowexec.exe is used in conjunction with ntvdm.exe to run old
16-bit applications.
[[MS-DOS and 16-bit Windows programs actually run as a Win32 process. The
program that creates the virtual MS-DOS environments for these to run in
(NTVDM.EXE) is a Win32 program. A virtual DOS machine (VDM) is created for
the program, so it thinks that it is running on a machine by itself.
However, the virtual machine is a normal 32-bit Windows NT process and is
subject to the same rules of preemptive multitasking as is other programs.
However, this only applies to MS-DOS programs. ]]
[[To run 16-bit Windows applications, NT uses a VDM that contains an extra
software layer called the Win16 on Win32 (WOW) layer. Although the VDM for
Windows shares some of the code for MS-DOS VDM, all Windows applications
share the same VDM. The reason this is done is to simulate the environment
that 16-bit Windows applications run in. Because Windows applications might
want to communicate with one another, a single VDM is used. Each 16-bit
application runs as a thread of the VDM; however, the WOW layers ensures
that only one of these threads is running at any given time. ]]
http://www.microsoft.com/technet/prodtechnol/winntas/evaluate/featfunc/windowsn.mspx#ETAA
Prefetch explanation...
[[Windows XP Professional monitors the files that are used when the computer
starts and when you start applications. By monitoring these files, Windows
XP Professional can prefetch them. Prefetching data is the process whereby
data that is expected to be requested is read ahead into the cache.
Prefetching boot files and applications decreases the time needed to start
Windows XP Professional and start applications.
Prefetching is further improved if the files are located next to each other
on the outer edge of the disk. Windows XP Professional optimizes the
location of boot files and applications when the computer is idle. The
optimization occurs in the background and lasts only a minute or two; you
might hear the hard disk being accessed when optimization occurs. After the
initial optimization takes place, subsequent optimization occurs, at most,
every three days.
When you run the Disk Defragmenter tools that are included with Windows XP
Professional, they can perform any optimization updates that are scheduled
to take place during the next idle period. The Disk Defragmenter tools do
not disturb the existing layout of optimized boot files and applications.
Note
Computers running Windows XP Home Edition also prefetch and optimize boot
files and applications.]]
Optimizing Startup Times by Using Defragmentation Tools
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/prkd_tro_uutk.asp
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In