Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!uw-june!uw-entropy!dataio!pilchuck!del
From: del@Data-IO.COM (Erik Lindberg)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Oooh Yeccheo. How Does This One Really Work?!?
Message-ID: <773@pilchuck.Data-IO.COM>
Date: 10 Dec 87 19:45:11 GMT
References: <164300022@uiucdcsb> <412@wa3wbu.UUCP> <13091@beta.UUCP>
Reply-To: del@pilchuck.Data-IO.COM (Erik Lindberg)
Organization: Data I/O Corporation; Redmond, WA
Lines: 43

In article <13091@beta.UUCP> myxm@beta.UUCP (Mike Mitchell) writes:
>I want to have a file called C:\AUTOEXEC.DDD that looks like this:
>
     ......
>rem Now I want the machine to do a Ctrl/Alt/Del Warmboot at this point
>reboot
>
>Now I get this when I turn the machie on! ...
>
><<CLEAR SCREEN>> <<HELLO COUNT RAM>> <<NOW HANG ON WHILE I BOOT TO DOS>>
>;c:\dos;c:\freen;c:\gunk
>Command not found

You have already seen (if paying attention) an explanation of *why* you saw
the behaviour you did. What you didn't see was an viable workaround that
left NO TRACE of it's previous presence. The previous poster suggested
running a "doit.bat", but then you are left with doit.bat still there and
no way to really delete it.

I take particular perverted pleasure in setting things like this up for folks,
so here is the best way I have determined to do it. Rename their config.sys
to config.ddd. Rename their autoexec.bat to autoexec.ddd. Install a config.sys
which uses device=vdisk.sys (or omit this if they already use a vdisk.sys
in config.sys). Determine which drive vdisk.sys will be installed as (by
rebooting if necessary). Lets assume the ram disk will be drive v:
Your new autoexec.bat should contain:

if not "%1" == "" goto doit
copy autoexec.bat v:
v:autoexec foobar

:doit
rem this is the real stuff.... insert your joke here
:exit
del config.sys
rename config.ddd config.sys
del autoexec.bat
rename autoexec.ddd autoexec.bat
reboot

-- 
del (Erik Lindberg) 
uw-beaver!tikal!pilchuck!del