Re: DOS Auto Boot Into Windows XP
- From: "Wesley Vogel" <123WVogel955@xxxxxxxxxxx>
- Date: Mon, 16 Jan 2006 12:20:00 -0700
Bugs,
>From my first post...
Restart the machine. Windows XP cannot be started from an MS-DOS disk.
> What can put in the autoexec.bat file that will trigger WinXP to
> load so I'll end up on the desktop??
Nothing. Basically, Windows XP needs to load from the hard drive. Restart
the machine. Windows XP does not and cannot start from autoexec.bat like
Windows 98 could. You have to restart the machine.
OK, I tried this. I put an MS-DOS startup disk in my A: drive and rebooted.
When I got to the A: prompt there was nothing I could do but hit the power
switch and restart the machine. Before I hit the power switch I replaced
the MS-DOS startup disk with a Windows XP start up disk that had boot.ini,
NTLDR and Ntdetect.com on it. When the machine re-powered, XP started.
Which proves absolutely nothing because XP would have restarted with no disk
in the A: drive. If that disk had not had Boot.ini, NTLDR and Ntdetect.com
on it I would have received a non-system disk error.
You have to restart the machine.
Since I have nothing better to do, I'll try to explain what I can. ;-)
That's not totally true, I should be paying bills, but this is more fun.
First, Windows XP is really Windows NT 5.1. XP runs on the NT kernel not
MS-DOS.
Boot.ini, NTLDR and Ntdetect.com are the only files needed for a Windows XP
boot disk, if not dual boot. And a Windows XP start up disk is only good if
something is wrong with the boot.ini, NTLDR and Ntdetect.com files that are
on the XP machine. It has no other useful purpose.
Bootsect.dos and Ntbootdd.sys would only be on an XP machine if it were set
up for a dual boot with MS-DOS or Windows 98 or older and if the hard drive
were formatted FAT32. MS-DOS will not install on a NTFS formatted drive.
Bootsect.dos and Ntbootdd.sys do not exist nor are they needed on XP. These
files would be as useful on an XP machine as something from a Mac.
Command.com
Himem.sys
IO.SYS
msdos.sys
Sys.com
autoexec.bat
Command.com is only needed for running old 16-bit MS-DOS programs in XP.
Use cmd.exe instead, after the machine has booted into XP. Command.com, on
XP, runs under NTVDM.exe (NT Virtual DOS Machine). Cmd.exe is XP's command
interpreter, it works similar to command.com, but not exactly the same.
Cmd.exe is also called Windows Command Processor or the Command Prompt.
Command.com is 16-bit and cannot handle long names only 8.3 short names.
Cmd.exe is 32-bit and can handle long or short names.
XP's MS-DOS subsystem uses a special version of Command.com that works
seamlessly with the other Windows XP subsystems (including piping and
redirection between subsystems). XP's command.com is not the same
command.com of earlier Windows versions. XP's command.com is specially
designed for Windows NT. When a command is entered for execution by
command.com, command.com does not actually execute it. Instead, it packages
the command text and sends it to CMD.EXE for execution.
Himem.sys exists on XP, only good for use in Config.nt, XP's version of
config.sys for running old 16-bit MS-DOS programs, serves no other useful
purpose on XP. Used with Devicehigh, Mem, Dos, Loadhigh, Dosonly and
Echoconfig commands in config.nt
IO.SYS exists on XP (0 bytes) does nothing as far as I can tell. Must be
there for running old 16-bit MS-DOS programs, serves no other useful purpose
on XP.
msdos.sys exists on XP (0 bytes) does nothing as far as I can tell. Must be
there for running old 16-bit MS-DOS programs, serves no other useful purpose
on XP.
Sys.com does not exist on XP. Command: Sys; New procedure or reason for
obsolescence: Windows XP does not fit on a standard 1.2 MB or 1.44 MB floppy
disk.
autoexec.bat exists on XP.
Windows XP uses Config.nt and Autoexec.nt, not Config.sys or Autoexec.bat.
Autoexec.bat in Windows XP can only be used for setting environment
variables or the path.
If you have a Config.sys or Autoexec.bat file XP will (mostly) ignore them.
Nothing in Config.sys will have any effect. Any line in Autoexec.bat that
launches a program or changes a directory will be ignored; the only lines in
Autoexec.bat that Windows XP will read are the lines that begin SET or PATH.
If ParseAutoexec is set to 1 in the registry.
Config.nt is used for the same kind of tasks formerly performed by
Config.sys (loading device drivers, etc.). Autoexec.nt is used for the same
kind of tasks formerly performed by Autoexec.bat (launching memory-resident
programs, etc.) Only old-style 16-bit DOS programs can be run from
Autoexec.nt. You cannot use Autoexec.nt to run 32-bit Windows XP text-mode
programs like MODE or SUBST; these programs may be run in an ordinary batch
file, but not in Autoexec.nt.
>From my AUTOEXEC.NT...
AUTOEXEC.BAT is not used to initialize the MS-DOS environment.
AUTOEXEC.NT is used to initialize the MS-DOS environment unless a
different startup file is specified in an application's PIF.
>From my CONFIG.NT...
CONFIG.SYS is not used to initialize the MS-DOS environment.
CONFIG.NT is used to initialize the MS-DOS environment unless a
different startup file is specified in an application's PIF.
[[One of the key design goals of Windows NT was compatibility with existing
applications. If Microsoft had decided to ignore this issue and concentrate
solely on performance, most (if not all) of the existing Windows and DOS
applications would have become useless. Because this would have meant
purchasing new applications, business might have opted to move completely
away from Microsoft. ]]
Because Microsoft didn't want to lose customers, they designed all NT
Operating Systems so that they would be able to run most, but not all, old
MS-DOS and Windows 95/98 programs.
You have to restart the machine.
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In news:Bug_zs.21pr1z@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx,
Bug_zs <Bug_zs.21pr1z@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> hunted and pecked:
> January 15, 2006
> Dear Wes,
>
> Thanks for the reply. I hope I can impose just a bit more. :)
>
> First a quickie about Ghost Image making/restoring in DOS. Before
>
> I got the "set comspec=c:\command.com etc.." "Formula", when Ghost
>
> was through either making or restoring an Image, the computer would
>
> just sit there with an A:\ prompt and I had to remove the floppy and
>
> turn off and on the box.
>
> By utilizing the formula, I just pop in a floppy and go about my
>
> business until I hear the opening theme music I have when my PC boots.
>
> With XP's non-relationship with DOS, that is now lost.
>
> However, in looking over that M$ document, my question to you now
> is:
>
> I make a formatted floppy via Windows XP with these files
>
> Boot.ini
> Bootsect.dos
> Ntbootdd.sys
> NTLDR
> Ntdetect.com
>
> I then add these files to the floppy:
>
> Command.com
> Himem.sys
> IO.SYS
> msdos.sys
> Sys.com
>
> AND an autoexec.bat file with the Ghost make (or restore) script on
> it.
>
> What can put in the autoexec.bat file that will trigger WinXP to
> load so
>
> I'll end up on the desktop??
>
>
> Bugs
>
>
> --
> Bug_zs
> ------------------------------------------------------------------------
> Bug_zs's Profile: http://www.highdots.com/forums/m1741
> View this thread: http://www.highdots.com/forums/t3204262
.
- Follow-Ups:
- Re: DOS Auto Boot Into Windows XP
- From: Wesley Vogel
- Re: DOS Auto Boot Into Windows XP
- References:
- DOS Auto Boot Into Windows XP
- From: Bug_zs
- Re: DOS Auto Boot Into Windows XP
- From: Wesley Vogel
- Re: DOS Auto Boot Into Windows XP
- From: Bug_zs
- DOS Auto Boot Into Windows XP
- Prev by Date: Re: Migrating files
- Next by Date: Re: my web items
- Previous by thread: Re: DOS Auto Boot Into Windows XP
- Next by thread: Re: DOS Auto Boot Into Windows XP
- Index(es):
Relevant Pages
|
