MSDOS Prompt

[Maurizio]

My MSDOS Prompt dpes not work any more. Pressing it from the menu causes nothing visible.
Left clicking the command.com file in the windows directory cuases a bynary browing of the file.
The same happens clicking any *.com executable.
Right clicking command.com does not offer the "Open" or "Execute" choices.
Any idea of what happened ? How can I restore the right association of the COM file types?
Thanks

[Maurizio]

Sorry to repeat my request, I have to specify better/more.
My WindowsME MSDOS Prompt does not work any more. Pressing it from the menu causes nothing visible happen.
Left clicking the command.com file in the windows directory causes a bynary browsing of the file.
The same happens clicking any *.com executable (like DISKCOPY) or trying to execute them form Start/Run.
Right clicking command.com does not offer the "Open" or "Execute" choices.
My MSDOS.SYS appears modified on 03/01/2003 and is 1.764 byte long.
I tryed to Extract MSDOS.SYS ffrom the WinME CABs without success.
Any idea of what happened ? How can I restore the right association of the COM file types?
Thanks

[Noel Paton]

try running SCANREG /FIX from a DOS prompt - windows will reboot.

See if that helps

--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
or
http://www.microsoft.com/presspass/features/2001/Mar01/Mar27pmvp.asp
"Maurizio" > wrote in message
...
> Sorry to repeat my request, I have to specify better/more.
> My WindowsME MSDOS Prompt does not work any more. Pressing it from the
menu causes nothing visible happen.
> Left clicking the command.com file in the windows directory causes a
bynary browsing of the file.
> The same happens clicking any *.com executable (like DISKCOPY) or trying
to execute them form Start/Run.
> Right clicking command.com does not offer the "Open" or "Execute" choices.
> My MSDOS.SYS appears modified on 03/01/2003 and is 1.764 byte long.
> I tryed to Extract MSDOS.SYS ffrom the WinME CABs without success.
> Any idea of what happened ? How can I restore the right association of the
COM file types?
> Thanks
>

[Maurizio]

Thank you for the suggestion: i typed "SCANREG /FIX" in the "RUN" window because I cannot reach a DOS prompt; neverthelles the DOS window opened to run the command and the system after rebooted coreectly, but the MSDOS Prompt is stll inoperative.

[Noel Paton]

File associations have nothing to do with MSDOS.SYS

You may have a virus/spyware hijack

download the Stinger from here and run it to make sure that A-V-disabling
viruses are not present on your PC
http://download.nai.com/products/mcafee-avert/stinger.exe

- update your virus scanner and run a full system scan of all files.

Reboot to Safe Mode and run CWShredder - to remove variants of the
CoolWebSearch hijacker.
http://www.merijn.org/cwschronicles.html

Use CWShredder, the removal tool:
http://www.merijn.org/files/cwshredder.zip
http://www.merijn.org/files/CWShredder.exe
http://www.spywareinfo.com/downloads/tools/CWShredder.exe
http://www.zerosrealm.com/downloads/CWShredder.zip

download AdAware from www.lavasoftusa.com, install, update, and run it to
remove spyware, adware,
and other such nasties from your system.


--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
or
http://www.microsoft.com/presspass/features/2001/Mar01/Mar27pmvp.asp
"Maurizio" > wrote in message
...
> Thank you for the suggestion: i typed "SCANREG /FIX" in the "RUN" window
because I cannot reach a DOS prompt; neverthelles the DOS window opened to
run the command and the system after rebooted coreectly, but the MSDOS
Prompt is stll inoperative.

[Maurizio]

Thanks for all your help; I tried all the suggested tools without success (nothing bad was found except some minor cookies).
MSDOS Prompt is still inoperative. I want to point out that if I try to click on the executable "EXE" in the Windows/Command directory, they are executed. If I try to click on the "COM" executable, the windows editor opens the the executable file in hexadecimal mode.
Maurizio
P.S. Could/Should I reinstall WinME form the CD on the actual version that I updated in the past five years? How should I proceed?

"Noel Paton" wrote:

> File associations have nothing to do with MSDOS.SYS
>
> You may have a virus/spyware hijack
>
> download the Stinger from here and run it to make sure that A-V-disabling
> viruses are not present on your PC
> http://download.nai.com/products/mcafee-avert/stinger.exe
>
> - update your virus scanner and run a full system scan of all files.
>
> Reboot to Safe Mode and run CWShredder - to remove variants of the
> CoolWebSearch hijacker.
> http://www.merijn.org/cwschronicles.html
>
> Use CWShredder, the removal tool:
> http://www.merijn.org/files/cwshredder.zip
> http://www.merijn.org/files/CWShredder.exe
> http://www.spywareinfo.com/downloads/tools/CWShredder.exe
> http://www.zerosrealm.com/downloads/CWShredder.zip
>
> download AdAware from www.lavasoftusa.com, install, update, and run it to
> remove spyware, adware,
> and other such nasties from your system.
>
>
> --
> Noel Paton (MS-MVP 2002-2004, Win9x)
>
> Nil Carborundum Illegitemi
> http://www.btinternet.com/~winnoel/millsrpch.htm
>
> Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
> or
> http://www.microsoft.com/presspass/features/2001/Mar01/Mar27pmvp.asp
> "Maurizio" > wrote in message
> ...
> > Thank you for the suggestion: i typed "SCANREG /FIX" in the "RUN" window
> because I cannot reach a DOS prompt; neverthelles the DOS window opened to
> run the command and the system after rebooted coreectly, but the MSDOS
> Prompt is stll inoperative.
>
>
>

[cquirke (MVP Win9x)]

On Wed, 16 Jun 2004 05:55:01 -0700, "Maurizio"

>MSDOS Prompt is still inoperative. I want to point out that if I try to click on the
>executable "EXE" in the Windows/Command directory, they are executed. If
>I try to click on the "COM" executable, the windows editor opens the the
>executable file in hexadecimal mode.

Oh, OK; then all that's wrong is you have a bad file association for
..COM files; most likely someone did a Shift-Rt-Click "Open With" and
forced these files to always run with Notepad or Edit.

>P.S. Could/Should I reinstall WinME form the CD on the actual
>version that I updated in the past five years?

No, that's a BAD IDEA.

>How should I proceed?

Start, Run, type RegEdit and Enter
Navigate into the registry as follows:
HKLEY_CLASSES_ROOT
.com
In the right pane you should see:
(Default) = "comfile"
Make it so if it was not so; links .com to the comfile type
Navigate into the registry as follows:
HKLEY_CLASSES_ROOT
comfile
shell
open
command
In the right pane, you should see:
(Default) = ""%1" %*"
Make it so if it was not so; runs the file as itself

That "%1" %* has to be VERY EXACT; no extra spaces, fluffed quote
levels etc. It should look exactly the same as what you see for
exefile on your system. "%1" means "this file" and the quotes are
required to bind spaces within path and name as a single parameter.
The %* presumably appends any command line parameters.

Looks like the command prompt is not running, simply because the
program file involved is a .com file (Command.com). You could prove
that to yourself by renaming it Command.exe and running that.

Be CAREFUL with "Open With". It's a chainsaw with teeth.



>-------------------- ----- ---- --- -- - - - -
No, perfection is not an entrance requirement.
We'll settle for integrity and humility
>-------------------- ----- ---- --- -- - - - -

[Maurizio]

Thank for your reply: I acted as you suggested and now the .COM work again.
Also "COMMAND.COM" works: nevertheless it works only if I click on it: if I use the DOS Prompt link from the menu or create and use a link to COMMAND.COM elsewhere, when I press it nothing apparently happens.
ANother thing: after using the COMMAND.COM window, when I enter "exit" to close it, it does not closes itself, but a message appears telling me to press CTRL+C (when doing so the window at last closes).
Looking into the register, I noticed that in the entry HKEY_CLASSES_ROOT, in the right panel appear two keys: one is the (Default) you mentioned, the other is "ZAMailSafeExt" with the value "zl6": apparently this comes from ZoneAlarm.
May be all this happend after one of the ZoneAlarm updates, but I have no clear evidence.
Do you have also suggestion for the COMMAND.COM link mistery? I tried to change various parameters of the PIF file without success.
Thanks again - Maurizio

"cquirke (MVP Win9x)" wrote:

> On Wed, 16 Jun 2004 05:55:01 -0700, "Maurizio"
>
> >MSDOS Prompt is still inoperative. I want to point out that if I try to click on the
> >executable "EXE" in the Windows/Command directory, they are executed. If
> >I try to click on the "COM" executable, the windows editor opens the the
> >executable file in hexadecimal mode.
>
> Oh, OK; then all that's wrong is you have a bad file association for
> ..COM files; most likely someone did a Shift-Rt-Click "Open With" and
> forced these files to always run with Notepad or Edit.
>
> >P.S. Could/Should I reinstall WinME form the CD on the actual
> >version that I updated in the past five years?
>
> No, that's a BAD IDEA.
>
> >How should I proceed?
>
> Start, Run, type RegEdit and Enter
> Navigate into the registry as follows:
> HKLEY_CLASSES_ROOT
> .com
> In the right pane you should see:
> (Default) = "comfile"
> Make it so if it was not so; links .com to the comfile type
> Navigate into the registry as follows:
> HKLEY_CLASSES_ROOT
> comfile
> shell
> open
> command
> In the right pane, you should see:
> (Default) = ""%1" %*"
> Make it so if it was not so; runs the file as itself
>
> That "%1" %* has to be VERY EXACT; no extra spaces, fluffed quote
> levels etc. It should look exactly the same as what you see for
> exefile on your system. "%1" means "this file" and the quotes are
> required to bind spaces within path and name as a single parameter.
> The %* presumably appends any command line parameters.
>
> Looks like the command prompt is not running, simply because the
> program file involved is a .com file (Command.com). You could prove
> that to yourself by renaming it Command.exe and running that.
>
> Be CAREFUL with "Open With". It's a chainsaw with teeth.
>
>
>
> >-------------------- ----- ---- --- -- - - - -
> No, perfection is not an entrance requirement.
> We'll settle for integrity and humility
> >-------------------- ----- ---- --- -- - - - -
>

[Shane]

> HKLEY_CLASSES_ROOT

Is this from the Ned Flanders school of registry editing then, Chris?


Shane

[Noel Paton]

There should be NO .pif file associated with COMMAND.COM!!!


--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
or
http://www.microsoft.com/presspass/features/2001/Mar01/Mar27pmvp.asp

"Maurizio" > wrote in message
...
> Thank for your reply: I acted as you suggested and now the .COM work
again.
> Also "COMMAND.COM" works: nevertheless it works only if I click on it: if
I use the DOS Prompt link from the menu or create and use a link to
COMMAND.COM elsewhere, when I press it nothing apparently happens.
> ANother thing: after using the COMMAND.COM window, when I enter "exit" to
close it, it does not closes itself, but a message appears telling me to
press CTRL+C (when doing so the window at last closes).
> Looking into the register, I noticed that in the entry HKEY_CLASSES_ROOT,
in the right panel appear two keys: one is the (Default) you mentioned, the
other is "ZAMailSafeExt" with the value "zl6": apparently this comes from
ZoneAlarm.
> May be all this happend after one of the ZoneAlarm updates, but I have no
clear evidence.
> Do you have also suggestion for the COMMAND.COM link mistery? I tried to
change various parameters of the PIF file without success.
> Thanks again - Maurizio
>
> "cquirke (MVP Win9x)" wrote:
>
> > On Wed, 16 Jun 2004 05:55:01 -0700, "Maurizio"
> >
> > >MSDOS Prompt is still inoperative. I want to point out that if I try to
click on the
> > >executable "EXE" in the Windows/Command directory, they are executed.
If
> > >I try to click on the "COM" executable, the windows editor opens the
the
> > >executable file in hexadecimal mode.
> >
> > Oh, OK; then all that's wrong is you have a bad file association for
> > ..COM files; most likely someone did a Shift-Rt-Click "Open With" and
> > forced these files to always run with Notepad or Edit.
> >
> > >P.S. Could/Should I reinstall WinME form the CD on the actual
> > >version that I updated in the past five years?
> >
> > No, that's a BAD IDEA.
> >
> > >How should I proceed?
> >
> > Start, Run, type RegEdit and Enter
> > Navigate into the registry as follows:
> > HKLEY_CLASSES_ROOT
> > .com
> > In the right pane you should see:
> > (Default) = "comfile"
> > Make it so if it was not so; links .com to the comfile type
> > Navigate into the registry as follows:
> > HKLEY_CLASSES_ROOT
> > comfile
> > shell
> > open
> > command
> > In the right pane, you should see:
> > (Default) = ""%1" %*"
> > Make it so if it was not so; runs the file as itself
> >
> > That "%1" %* has to be VERY EXACT; no extra spaces, fluffed quote
> > levels etc. It should look exactly the same as what you see for
> > exefile on your system. "%1" means "this file" and the quotes are
> > required to bind spaces within path and name as a single parameter.
> > The %* presumably appends any command line parameters.
> >
> > Looks like the command prompt is not running, simply because the
> > program file involved is a .com file (Command.com). You could prove
> > that to yourself by renaming it Command.exe and running that.
> >
> > Be CAREFUL with "Open With". It's a chainsaw with teeth.
> >
> >
> >
> > >-------------------- ----- ---- --- -- - - - -
> > No, perfection is not an entrance requirement.
> > We'll settle for integrity and humility
> > >-------------------- ----- ---- --- -- - - - -
> >

[Maurizio]

You are right, I used the very old terminology: I intended the link to command.com.

"Noel Paton" wrote:

> There should be NO .pif file associated with COMMAND.COM!!!
>
>
> --
> Noel Paton (MS-MVP 2002-2004, Win9x)
>
> Nil Carborundum Illegitemi
> http://www.btinternet.com/~winnoel/millsrpch.htm
>
> Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
> or
> http://www.microsoft.com/presspass/features/2001/Mar01/Mar27pmvp.asp
>
> "Maurizio" > wrote in message
> ...
> > Thank for your reply: I acted as you suggested and now the .COM work
> again.
> > Also "COMMAND.COM" works: nevertheless it works only if I click on it: if
> I use the DOS Prompt link from the menu or create and use a link to
> COMMAND.COM elsewhere, when I press it nothing apparently happens.
> > ANother thing: after using the COMMAND.COM window, when I enter "exit" to
> close it, it does not closes itself, but a message appears telling me to
> press CTRL+C (when doing so the window at last closes).
> > Looking into the register, I noticed that in the entry HKEY_CLASSES_ROOT,
> in the right panel appear two keys: one is the (Default) you mentioned, the
> other is "ZAMailSafeExt" with the value "zl6": apparently this comes from
> ZoneAlarm.
> > May be all this happend after one of the ZoneAlarm updates, but I have no
> clear evidence.
> > Do you have also suggestion for the COMMAND.COM link mistery? I tried to
> change various parameters of the PIF file without success.
> > Thanks again - Maurizio
> >
> > "cquirke (MVP Win9x)" wrote:
> >
> > > On Wed, 16 Jun 2004 05:55:01 -0700, "Maurizio"
> > >
> > > >MSDOS Prompt is still inoperative. I want to point out that if I try to
> click on the
> > > >executable "EXE" in the Windows/Command directory, they are executed.
> If
> > > >I try to click on the "COM" executable, the windows editor opens the
> the
> > > >executable file in hexadecimal mode.
> > >
> > > Oh, OK; then all that's wrong is you have a bad file association for
> > > ..COM files; most likely someone did a Shift-Rt-Click "Open With" and
> > > forced these files to always run with Notepad or Edit.
> > >
> > > >P.S. Could/Should I reinstall WinME form the CD on the actual
> > > >version that I updated in the past five years?
> > >
> > > No, that's a BAD IDEA.
> > >
> > > >How should I proceed?
> > >
> > > Start, Run, type RegEdit and Enter
> > > Navigate into the registry as follows:
> > > HKLEY_CLASSES_ROOT
> > > .com
> > > In the right pane you should see:
> > > (Default) = "comfile"
> > > Make it so if it was not so; links .com to the comfile type
> > > Navigate into the registry as follows:
> > > HKLEY_CLASSES_ROOT
> > > comfile
> > > shell
> > > open
> > > command
> > > In the right pane, you should see:
> > > (Default) = ""%1" %*"
> > > Make it so if it was not so; runs the file as itself
> > >
> > > That "%1" %* has to be VERY EXACT; no extra spaces, fluffed quote
> > > levels etc. It should look exactly the same as what you see for
> > > exefile on your system. "%1" means "this file" and the quotes are
> > > required to bind spaces within path and name as a single parameter.
> > > The %* presumably appends any command line parameters.
> > >
> > > Looks like the command prompt is not running, simply because the
> > > program file involved is a .com file (Command.com). You could prove
> > > that to yourself by renaming it Command.exe and running that.
> > >
> > > Be CAREFUL with "Open With". It's a chainsaw with teeth.
> > >
> > >
> > >
> > > >-------------------- ----- ---- --- -- - - - -
> > > No, perfection is not an entrance requirement.
> > > We'll settle for integrity and humility
> > > >-------------------- ----- ---- --- -- - - - -
> > >
>
>
>

[cquirke (MVP Win9x)]

On Fri, 18 Jun 2004 10:55:01 -0700, "Maurizio"

>Thank for your reply: I acted as you suggested and now the .COM work again.
>Also "COMMAND.COM" works:

Good; we're getting there!

>nevertheless it works only if I click on it: if I use the DOS Prompt link
>from the menu or create and use a link to COMMAND.COM elsewhere,
>when I press it nothing apparently happens.

There are several .pif that apply to C:\Command.com and/or the
Command.com in the Windows base dir. Some are in the same location
and called Command.pif; these apply when you run Command.com directly
via Windows (they too will be ignored in DOS mode) unless some
AppPaths chicanery is doing a redirect. Others have different names,
e.g. "Command Prompt" etc.

If some of those .pif are bad, you'd get your mileage. The fis would
be to rename away the bad .pif and re-generate them.

>ANother thing: after using the COMMAND.COM window, when I enter
>"exit" to close it, it does not closes itself, but a message appears
>telling me to press CTRL+C (when doing so the window at last closes).

That I have seen, and not always been able to find a cause for. On
the face of it, this can be expected if the Command session spawned a
TSR (Terminate and Stay Resident) app - including a malware. OTOH you
may find no trace of that, and still have the hassle.

I see this is a WinME newsgroup, and that adds an extra wrinkle. When
you run a command prompt in WinME, there's an associated .BAT that is
run (even though no .BAT is set in the .pif's Properties). If there
are problems in that .BAT, then etc. - I can't recall the name of the
..BAT, but Mike Maltby or Noel will know :-)

>Looking into the register, I noticed that in the entry
>HKEY_CLASSES_ROOT, in the right panel appear two keys: one
>is the (Default) you mentioned, the other is "ZAMailSafeExt" with
>the value "zl6": apparently this comes from ZoneAlarm.

Yep. That won't affect what we are dealing with here - only Zone
Alarm looks for that registry information, and uses it as the
alternate extension to spoof incoming attachments of that type so that
they can't run. Crude, but works!

>Do you have also suggestion for the COMMAND.COM link mistery?

You won't likely find a Command.lnk unless you'd renamed Command.com
to (say) Command.exe or Command.scr at the time your .com association
was broken. DOS executables spawn .pif shortcuts, not .lnk, and .com
and .bat files are always treated as DOS rather than Windows
executables (at least in Win95/98/ME).

>I tried to change various parameters of the PIF file without success.

Do the .pif look sane? If they look binary, suspect raw malware code
that's been dropped as a ".pif". Remember, not all the .pif you seek
are called Command.pif, and the associated .BAT factor (the .BAT may
have a .pif of its own; check that too!)



>-------------------- ----- ---- --- -- - - - -
No, perfection is not an entrance requirement.
We'll settle for integrity and humility
>-------------------- ----- ---- --- -- - - - -

[cquirke (MVP Win9x)]

On Fri, 18 Jun 2004 19:08:46 +0100, "Shane"

>> HKLEY_CLASSES_ROOT
>
>Is this from the Ned Flanders school of registry editing then, Chris?

<blush> Typo detected: Ritual finger amputation performed :-)




>-------------------- ----- ---- --- -- - - - -
No, perfection is not an entrance requirement.
We'll settle for integrity and humility
>-------------------- ----- ---- --- -- - - - -

[Noel Paton]

Ooops - you're right!
(Here was me, thinking that .pif files had gone the way of the
dinosaurs!<g>)
My system has three relevant .pif files -
C:\Windows\..
Command.pif ( target COMMAND.COM)
DOSPRMPT.pif (target C:\Windows\COMMAND.COM)
Also - in the Start Menu, the .pif is 'MS-DOS Prompt.pif' (target
C:\Windows\COMMAND.COM)
..
I can't find the BAT file you're talking about, Chris - are you sure about
that? - remember that ME's PIF properties include stuff that isn't in the 98
set AFAIK.


--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
or
http://www.microsoft.com/presspass/features/2001/Mar01/Mar27pmvp.asp

"cquirke (MVP Win9x)" > wrote in message
...
> On Fri, 18 Jun 2004 10:55:01 -0700, "Maurizio"
>
> >Thank for your reply: I acted as you suggested and now the .COM work
again.
> >Also "COMMAND.COM" works:
>
> Good; we're getting there!
>
> >nevertheless it works only if I click on it: if I use the DOS Prompt link
> >from the menu or create and use a link to COMMAND.COM elsewhere,
> >when I press it nothing apparently happens.
>
> There are several .pif that apply to C:\Command.com and/or the
> Command.com in the Windows base dir. Some are in the same location
> and called Command.pif; these apply when you run Command.com directly
> via Windows (they too will be ignored in DOS mode) unless some
> AppPaths chicanery is doing a redirect. Others have different names,
> e.g. "Command Prompt" etc.
>
> If some of those .pif are bad, you'd get your mileage. The fis would
> be to rename away the bad .pif and re-generate them.
>
> >ANother thing: after using the COMMAND.COM window, when I enter
> >"exit" to close it, it does not closes itself, but a message appears
> >telling me to press CTRL+C (when doing so the window at last closes).
>
> That I have seen, and not always been able to find a cause for. On
> the face of it, this can be expected if the Command session spawned a
> TSR (Terminate and Stay Resident) app - including a malware. OTOH you
> may find no trace of that, and still have the hassle.
>
> I see this is a WinME newsgroup, and that adds an extra wrinkle. When
> you run a command prompt in WinME, there's an associated .BAT that is
> run (even though no .BAT is set in the .pif's Properties). If there
> are problems in that .BAT, then etc. - I can't recall the name of the
> .BAT, but Mike Maltby or Noel will know :-)
>
> >Looking into the register, I noticed that in the entry
> >HKEY_CLASSES_ROOT, in the right panel appear two keys: one
> >is the (Default) you mentioned, the other is "ZAMailSafeExt" with
> >the value "zl6": apparently this comes from ZoneAlarm.
>
> Yep. That won't affect what we are dealing with here - only Zone
> Alarm looks for that registry information, and uses it as the
> alternate extension to spoof incoming attachments of that type so that
> they can't run. Crude, but works!
>
> >Do you have also suggestion for the COMMAND.COM link mistery?
>
> You won't likely find a Command.lnk unless you'd renamed Command.com
> to (say) Command.exe or Command.scr at the time your .com association
> was broken. DOS executables spawn .pif shortcuts, not .lnk, and .com
> and .bat files are always treated as DOS rather than Windows
> executables (at least in Win95/98/ME).
>
> >I tried to change various parameters of the PIF file without success.
>
> Do the .pif look sane? If they look binary, suspect raw malware code
> that's been dropped as a ".pif". Remember, not all the .pif you seek
> are called Command.pif, and the associated .BAT factor (the .BAT may
> have a .pif of its own; check that too!)
>
>
>
> >-------------------- ----- ---- --- -- - - - -
> No, perfection is not an entrance requirement.
> We'll settle for integrity and humility
> >-------------------- ----- ---- --- -- - - - -

[Maurizio]

Thanks to you all.
I found an empty DosStart.bat. I tryed to put the line "c:\windows\command.com" in it and discovered that again the system editor opens when clicking on it.
So do all my BAT files!!
I investigated with the registry editor and the HKEY_CLASSES_ROOT/.bat entry has a "Default" key with value "batfile".
The entry HKEY_CLASSES_ROOT/batfile/shell miss the key "open" while has the key "edit" with value "C:\WINDOWS\NOTEPAD.EXE %1".

a) Should I add an entry for the key "open" and with which value?
b) What should really contain the DosStart.bat file?
Your help and spirit is highly appreciated.
Maurizio
"cquirke (MVP Win9x)" wrote:

> On Fri, 18 Jun 2004 19:08:46 +0100, "Shane"
>
> >> HKLEY_CLASSES_ROOT
> >
> >Is this from the Ned Flanders school of registry editing then, Chris?
>
> <blush> Typo detected: Ritual finger amputation performed :-)
>
>
>
>
> >-------------------- ----- ---- --- -- - - - -
> No, perfection is not an entrance requirement.
> We'll settle for integrity and humility
> >-------------------- ----- ---- --- -- - - - -
>

[Maurizio]

Thanks to all.
I found an empty DosStart.bat. I inserted the line "c:\windows\command.com" and tryed to click on it: the editor opened it in hexadecimal mode. So do all my "BAT" files !!
I investigate the registry and found that the entry HKEY_CLASSES_ROOT/.bat has the key "Default" with value "batfile".
The entry HKEY_CLASSES_ROOT/batfile/shell miss the key "open/command" while has the key "edit/command" with the "Default" value of "C:\WINDOWS\NOTEPAD.EXE %1".
a) Should I add the "open/command" key and with which "Default" value?
b) What should really contain the "DosStart.bat"?
Thank for your help and spirit.
Maurizio

"cquirke (MVP Win9x)" wrote:

> On Fri, 18 Jun 2004 19:08:46 +0100, "Shane"
>
> >> HKLEY_CLASSES_ROOT
> >
> >Is this from the Ned Flanders school of registry editing then, Chris?
>
> <blush> Typo detected: Ritual finger amputation performed :-)
>
>
>
>
> >-------------------- ----- ---- --- -- - - - -
> No, perfection is not an entrance requirement.
> We'll settle for integrity and humility
> >-------------------- ----- ---- --- -- - - - -
>

[cquirke (MVP Win9x)]

On Sat, 19 Jun 2004 14:03:10 +0100, "Noel Paton"

>I can't find the BAT file you're talking about, Chris - are you sure about
>that? - remember that ME's PIF properties include stuff that isn't in the 98
>set AFAIK.

Yep, I think it's called CMDINST.BAT, and it's where one sets up
things like DOSKey etc. (Alex Nichol has a way of getting that to work
with Command.com as a rt-click Drive or Directory action).

It's not pointed to as the "batch file" in the .pif; WinME uses it
"directly" as the way it launches Command.com



>-------------------- ----- ---- --- -- - - - -
No, perfection is not an entrance requirement.
We'll settle for integrity and humility
>-------------------- ----- ---- --- -- - - - -

[cquirke (MVP Win9x)]

On Sat, 19 Jun 2004 07:47:01 -0700, "Maurizio"

>I found an empty DosStart.bat

Nothing in WinME will use that automatically - it's used by the "Use
with current..." mechanism of booting into pure DOS mode that was
removed from WinME.

>I tryed to put the line "c:\windows\command.com" in it and
>discovered that again the system editor opens when clicking on it.
>So do all my BAT files!!

Cue RegEdit, HKEY_CLASSES_ROOT\.bat and HKEY_CLASSES_ROOT\batfile

>I investigated with the registry editor and the HKEY_CLASSES_ROOT/.bat
>entry has a "Default" key with value "batfile".

Good. But...

>The entry HKEY_CLASSES_ROOT/batfile/shell miss the key "open"

Create a new "open" as ""%1" %*" exactly as shown. Deja vu; are you
the same dude who had a barfed .com -> comfile association? If so,
see the reply to that for the shape of how to fix this :-)

>while has the key "edit" with value "C:\WINDOWS\NOTEPAD.EXE %1".

That's correct - for the "edit" action.



>-------------------- ----- ---- --- -- - - - -
No, perfection is not an entrance requirement.
We'll settle for integrity and humility
>-------------------- ----- ---- --- -- - - - -

[Noel Paton]

OK - that gives me an excuse to fire up my nice new clean copy of ME in
VPC<g>
Nope no CMDINST.BAT
there's a CMDINIT.BAT - which just contains a doskey command
(now that's interesting - doing a search for '.dos' gives a full file list
of all files wherever on the PC, AFAICT)


--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
or
http://www.microsoft.com/presspass/features/2001/Mar01/Mar27pmvp.asp

"cquirke (MVP Win9x)" > wrote in message
...
> On Sat, 19 Jun 2004 14:03:10 +0100, "Noel Paton"
>
> >I can't find the BAT file you're talking about, Chris - are you sure
about
> >that? - remember that ME's PIF properties include stuff that isn't in the
98
> >set AFAIK.
>
> Yep, I think it's called CMDINST.BAT, and it's where one sets up
> things like DOSKey etc. (Alex Nichol has a way of getting that to work
> with Command.com as a rt-click Drive or Directory action).
>
> It's not pointed to as the "batch file" in the .pif; WinME uses it
> "directly" as the way it launches Command.com
>
>
>
> >-------------------- ----- ---- --- -- - - - -
> No, perfection is not an entrance requirement.
> We'll settle for integrity and humility
> >-------------------- ----- ---- --- -- - - - -

[Maurizio]

Yes, Y was the one with the corrupted .com entry.
I already addedd the HKEY_CLASSES_ROOT/batfile/open key as instructed.
The DosStart.bat as modified by me (c:\windows\command.com) now opens the
DOS prompt. Still unable to make the DosPrompt link to "command.com" work.
While clicking on command.com opens the DOS prompt, any link (old or new) to command.com apparently does nothing.
Also a link to the DosStart.bat seems inoperative!
I noticed that in the registry there is also the HKEY_CLASSES_ROOT/cmdfile: does this entry by chance also require the shell/command/open key?
I wonder what could have caused all this mess, while my first suspect is one of the recent ZoneAlermPro update.
"cquirke (MVP Win9x)" wrote:

> On Sat, 19 Jun 2004 07:47:01 -0700, "Maurizio"
>
> >I found an empty DosStart.bat
>
> Nothing in WinME will use that automatically - it's used by the "Use
> with current..." mechanism of booting into pure DOS mode that was
> removed from WinME.
>
> >I tryed to put the line "c:\windows\command.com" in it and
> >discovered that again the system editor opens when clicking on it.
> >So do all my BAT files!!
>
> Cue RegEdit, HKEY_CLASSES_ROOT\.bat and HKEY_CLASSES_ROOT\batfile
>
> >I investigated with the registry editor and the HKEY_CLASSES_ROOT/.bat
> >entry has a "Default" key with value "batfile".
>
> Good. But...
>
> >The entry HKEY_CLASSES_ROOT/batfile/shell miss the key "open"
>
> Create a new "open" as ""%1" %*" exactly as shown. Deja vu; are you
> the same dude who had a barfed .com -> comfile association? If so,
> see the reply to that for the shape of how to fix this :-)
>
> >while has the key "edit" with value "C:\WINDOWS\NOTEPAD.EXE %1".
>
> That's correct - for the "edit" action.
>
>
>
> >-------------------- ----- ---- --- -- - - - -
> No, perfection is not an entrance requirement.
> We'll settle for integrity and humility
> >-------------------- ----- ---- --- -- - - - -
>

[Mike M]

> there's a CMDINIT.BAT

That's it. As Chris said he "thought" cmndinst.bat but as you've found it is
cmninit.bat
--
Mike Maltby MS-MVP



Noel Paton > wrote:

> OK - that gives me an excuse to fire up my nice new clean copy of ME in
> VPC<g>
> Nope no CMDINST.BAT
> there's a CMDINIT.BAT - which just contains a doskey command
> (now that's interesting - doing a search for '.dos' gives a full file list
> of all files wherever on the PC, AFAICT)

[Noel Paton]

Duh? There's naff-all in that except a reference to doskey (@echo off :
doskey /insert > nul)- and running it by itself brings up a DOS window with
the message....

'MICROSOFT WINDOWS POP-UP PROGRAM SUPPORT'
'Your pop-up program is ready to run. When you have finished using it, press
Ctrl+c to close this window and return to Windows'



--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
or
http://www.microsoft.com/presspass/features/2001/Mar01/Mar27pmvp.asp

"Mike M" > wrote in message
...
> > there's a CMDINIT.BAT
>
> That's it. As Chris said he "thought" cmndinst.bat but as you've found it
is
> cmninit.bat
> --
> Mike Maltby MS-MVP
>
>
>
> Noel Paton > wrote:
>
> > OK - that gives me an excuse to fire up my nice new clean copy of ME in
> > VPC<g>
> > Nope no CMDINST.BAT
> > there's a CMDINIT.BAT - which just contains a doskey command
> > (now that's interesting - doing a search for '.dos' gives a full file
list
> > of all files wherever on the PC, AFAICT)
>
>

[cquirke (MVP Win9x)]

On Sat, 19 Jun 2004 21:43:33 +0100, "Noel Paton"

>OK - that gives me an excuse to fire up my nice new clean copy of ME in
>VPC<g>
>Nope no CMDINST.BAT
>there's a CMDINIT.BAT - which just contains a doskey command

That's the one I mean!



>-------------------- ----- ---- --- -- - - - -
No, perfection is not an entrance requirement.
We'll settle for integrity and humility
>-------------------- ----- ---- --- -- - - - -

[Maurizio]

I solved my last problem with the DOS Prompt working only if the command .com is clicked directly or invoked from the Start/Execute panel and not from whatever link I could build to it: I realized that also the entry HKEY_CLASSES_ROOT/piffile missed the subkey open/command with the predefined value of ("%1" %*).
I added this key and now it works again.
Still unknown tha cause of this mess in the register; all the altered keys discovered are related to the execution of the DOS commands.
People at ZoneLAb deny any responsability on that.
Thanks again for your precious help; now I know that the PCs should be bought in couple, so that the user can maintain an original copy of the system SW !?
"cquirke (MVP Win9x)" wrote:

> On Sat, 19 Jun 2004 07:47:01 -0700, "Maurizio"
>
> >I found an empty DosStart.bat
>
> Nothing in WinME will use that automatically - it's used by the "Use
> with current..." mechanism of booting into pure DOS mode that was
> removed from WinME.
>
> >I tryed to put the line "c:\windows\command.com" in it and
> >discovered that again the system editor opens when clicking on it.
> >So do all my BAT files!!
>
> Cue RegEdit, HKEY_CLASSES_ROOT\.bat and HKEY_CLASSES_ROOT\batfile
>
> >I investigated with the registry editor and the HKEY_CLASSES_ROOT/.bat
> >entry has a "Default" key with value "batfile".
>
> Good. But...
>
> >The entry HKEY_CLASSES_ROOT/batfile/shell miss the key "open"
>
> Create a new "open" as ""%1" %*" exactly as shown. Deja vu; are you
> the same dude who had a barfed .com -> comfile association? If so,
> see the reply to that for the shape of how to fix this :-)
>
> >while has the key "edit" with value "C:\WINDOWS\NOTEPAD.EXE %1".
>
> That's correct - for the "edit" action.
>
>
>
> >-------------------- ----- ---- --- -- - - - -
> No, perfection is not an entrance requirement.
> We'll settle for integrity and humility
> >-------------------- ----- ---- --- -- - - - -
>