Go Back   Cyber Tech Help Support Forums > Operating Systems > Older Windows Versions > Windows 98

Notices

Reply
 
Topic Tools
  #1  
Old November 25th, 2000, 03:22 AM
Lloyd Lloyd is offline
Member
 
Join Date: Nov 2000
Location: Glendale, WI., USA
Age: 53
Posts: 42
Bad command or file name

I recently restarted in ms dos mode, & got this on my screen, pardon the length, but I want to include everything:

C:\>
C:\>
LH C:\PROGRA~1\MICROS~2|MOUSE\MOUSE.EXE
BAD COMMAND OR FILE NAME
C:\>C:\ESSOLO.COM
ESS PCI AUDIO DOS DEVICE SETUP UTILITY, VERSION 2.11A
(c) ESS Technology, Inc., 1996-1998 All rights reserved
SOLO
DMA MODE IS ALI DDMA
INCORRECT RESOURCE ASSIGNMENT

C:\>

MICROSOFT (R) WINDOWS 98
(C) copyright Microsoft Corp 1981-1999

C:\WINDOWS>

I then went about what I wanted to do in ms dos, rebooted and everythings fine. I'm curious about the bad command or file name, and the incorrect resource assignment messages. Now for my attempt at the answer, I recently installed drivers for an intellimouse. Since my last re-installation of 98, about a month ago, I had been using the mouse drivers windows installed. Is this windows looking for the drivers it thought my mouse was using? Is it anything to worry about? Thanks for any advice.
Reply With Quote


  #2  
Old November 25th, 2000, 05:58 AM
Junky Junky is offline
CTH Subscriber
 
Join Date: Oct 2000
Location: Oregon, USA
Posts: 3,705
Hi,

Actually, windows98 doesn't even need an autoexec.bat or a config.sys to run properly. So you can disable a line in either of the files by putting a "rem" then a space in front of that line for the mouse and the same for the DMA MODE line. That way those lines will not be taken as a command. Reboot and load windows and see if all is well. If so, just leave those lines with the "rem" alone. You can always go back later if you want and take the "rem" out and those lines will ack as a command again.

Even if you just leave it the way it is there shouldn't be any harm in it. As long as windows is running OK that is.

To edit either the autoexec.bat or config.sys click on START, then on RUN and type in "sysedit". There will be windows that pop open. Edit them there and save. Like I said, you can always go back later and change them back.

[This message has been edited by Junky (edited 24 November 2000).]
Reply With Quote
  #3  
Old November 25th, 2000, 06:40 AM
MishY's Avatar
MishY MishY is offline
Cyber Tech Help Administrator
 
Join Date: Sep 2000
O/S: Windows 7 64-bit
Location: England
Age: 33
Posts: 8,879
Blog Entries: 2
Just an addition....

Bad command or filename errors like the one you mentioned above are "usually" because of incorrect syntax, or the path to the file being loaded is incorrect

MiShY

------------------
Cyber Tech Help
You Break 'em - We Fix 'em
Reply With Quote
  #4  
Old November 25th, 2000, 05:18 PM
Lloyd Lloyd is offline
Member
 
Join Date: Nov 2000
Location: Glendale, WI., USA
Age: 53
Posts: 42
Thanks for the response, but now I'm a little more confused. This is what's in my autoexec.bat:

@C:\PROGRA~1\NORTON~1\NAVDX.EXE /Startup
C:\essolo.com

And this is my config.sys:
DEVICE=C:\essolo.sys /s:8888125D

There is no mention of either the mouse, or the dma mode. Also (in response to Mishy), I didn't type in those commands, that led to the bad command or file name, and the incorrect resource assignment. They came up on their own, when I restarted in ms dos........Still curious.

Reply With Quote
  #5  
Old November 26th, 2000, 02:08 AM
smurfy's Avatar
smurfy smurfy is offline
Cyber Tech Help Moderator
 
Join Date: Sep 2000
O/S: Linux
Location: Christchurch New Zealand
Posts: 8,447
Look here and here

When you restart your computer by choosing the "Restart the computer in MS-DOS mode" option in the Shut Down Windows dialog box, Windows closes all running programs, removes itself from memory, and then starts a real- mode command prompt. If the Use Current MS-DOS Configuration option is selected in the "Exit to DOS.pif" file that is used to restart the computer in MS-DOS mode, the Dosstart.bat file in the Windows folder is processed. If the Specify A New MS-DOS Configuration option is selected, the Config.sys and Autoexec.bat files listed in the "Exit to DOS.pif" file are used instead of the Config.sys and Autoexec.bat files in the root folder.


------------------
Smurfy
Suggest A Fix & CyberTech Help moderator.
smurfynz@netscape.net
Reply With Quote
  #6  
Old November 26th, 2000, 05:46 AM
Junky Junky is offline
CTH Subscriber
 
Join Date: Oct 2000
Location: Oregon, USA
Posts: 3,705
Good eyes smurfy! I read your post, then re-read the original post by Lloyd, didn't catch the part about "I recently restarted in ms dos mode, & got this on my screen, pardon the length, but I want to include everything:"

Just to add a comment or two:

Lloyd, click on START then on FIND and type in "dosstart.bat", then right click on it while holding down the shift key, then choose OPEN WITH and scroll down to Note Pad and open it.

Now you can view what is listed in there. You can place "rem" in front of a line you don't want executed.

This dosstart.bat file acts just like the autoexec.bat does when you first boot to a dos prompt, only it is ran when you exit out of windows to the MS-Dos prompt. They are independent of each other.

Hope I helped out here.
Reply With Quote
  #7  
Old November 26th, 2000, 10:05 PM
Lloyd Lloyd is offline
Member
 
Join Date: Nov 2000
Location: Glendale, WI., USA
Age: 53
Posts: 42
Thanks everyone for the responses. I think I really picked up a lot going through this. Originally, I didn't necessarily want, or not want, anything in particular being executed while restarting in MS Dos mode. I was just curious about those messages. I did put rem in front of the mouse line in dosstart.bat, and that bad command message no longer appears. The incorrect resource assignment one "fixed" itself, it now goes on to show current solo pci irq, sbpro game settings, etc. Don't know why that happened the first time. I did find that if I followed the path for the mouse, there was a mouse32.exe, not a mouse.exe as the path suggested. Hence the bad command or file name? From what I gather, if I wanted to have the mouse drivers loaded, I should change the path to mouse32.exe, and that would have cured that. I guess that answered it for me! Thanks to all who responded, these forums are really a good place to pick up stuff. Hopefully I'll be able to point someone else in the right direction someday soon! I'll just keep on trying!
Reply With Quote
  #8  
Old November 27th, 2000, 06:24 AM
Junky Junky is offline
CTH Subscriber
 
Join Date: Oct 2000
Location: Oregon, USA
Posts: 3,705
That's good news Lloyd. Keep on keeping on.
Reply With Quote
Reply

Bookmarks

Topic Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump




All times are GMT +1. The time now is 04:53 AM.