Go Back   PCMech Forums > Windows Support > Windows Legacy Support (XP and earlier)

Need Some Help? Type Your Keywords Here:

Reply
 
LinkBack Thread Tools Search this Thread Rate Thread Display Modes
Old 07-12-2003, 01:26 AM   #1
Member (8 bit)
 
plumerjr's Avatar
 
Join Date: Nov 2002
Location: Providence,RI
Posts: 156
Send a message via Yahoo to plumerjr
Question "Too many parameters" ?

During start-up i get this message right after it says device driver for cd-rom is loaded. Windows(98se) continues to load and there appears to be no problem. What parameters are they talking about and should I be worried about this. If I should be worried what can I do. Any info would be appreciated, thank you.
plumerjr is offline   Reply With Quote
Old 07-12-2003, 06:47 AM   #2
Member (14 bit)
Premium Member
 
TwoRails's Avatar
 
Join Date: Jan 2002
Location: The Great NorthWest
Posts: 12,594
Sounds like a bad command line in your Autoexec.bat file. I could be nothing if everything is working OK. Did you install a new program lately? Some times they will mess with things they shouldn't...
TwoRails is offline   Reply With Quote
Old 07-12-2003, 10:26 AM   #3
Member (8 bit)
 
plumerjr's Avatar
 
Join Date: Nov 2002
Location: Providence,RI
Posts: 156
Send a message via Yahoo to plumerjr
@ECHO OFF
SET BLASTER=A220 I7 D1 H7 P330 T6
SET SBPCI=C:\PROGRA~1\CREATIVE\AUDIO\DOSDRV
PROMPT $P$G
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;C:\CDROM;C:\BRCD\BIN;C:\BRCD\COMMAND;C:\Program Files\Executive Software\DiskeeperWorkstation\

REM --- By HiSpeed CD-ROM Drive installation program. 8/11/102 ---
rem - By Windows Setup - C:\WINDOWS\COMMAND\MSCDEX.EXE /D:MSC

I opened up autoexec.bat and this is what I have. I just installed Diskeeper, so perhaps that is the culprit. I'm just concerned if this is going to cause problems in the future.If you see a bad command line let me know. They could be staring me right in the face and I wouldn't know it.

Last edited by plumerjr; 07-12-2003 at 10:30 AM.
plumerjr is offline   Reply With Quote
Old 07-12-2003, 12:59 PM   #4
Member (12 bit)
 
andyms18a's Avatar
 
Join Date: Dec 2002
Location: essex
Posts: 2,252
try typing rem be for this line PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;C:\CDROM;C:\BRCD\BIN;C:\BRCD\COMMAND;C:\Program Files\Executive Software\DiskeeperWorkstation so it reads
@ECHO OFF
SET BLASTER=A220 I7 D1 H7 P330 T6
SET SBPCI=C:\PROGRA~1\CREATIVE\AUDIO\DOSDRV
PROMPT $P$G
rem PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;C:\CDROM;C:\BRCD\BIN;C:\BRCD\COMMAND;C:\Program Files\Executive Software\DiskeeperWorkstation

REM --- By HiSpeed CD-ROM Drive installation program. 8/11/102 ---
rem - By Windows Setup - C:\WINDOWS\COMMAND\MSCDEX.EXE /D:MSC
__________________
Join the PcMech.com Folding@Home Team and Help Save Lives! Click Here!
Life only looks greener on the other side of the fence
andyms18a is offline   Reply With Quote
Old 07-12-2003, 03:07 PM   #5
Member (12 bit)
 
Join Date: Nov 2001
Location: Woodland Hills, CA (suburb of Los Angeles)
Posts: 4,014
I'd guess that you're right in your hunch that it's the Diskeeper line that's causing the message. I'd also guess that andy is right figuring it's that the Path= statements have gone on a little too long. Removing that line probably would stop that error message. I suppose you could just break the command into two separate lines, too:
something like:
Path=C:\Windows;C:\Windows\Command;C:\;C:\CDROM;C:\BRCD\BiIN;C:\BRCD\COMMAND
Path=C:\Program Files\Executive Software\DiskeeperWorkstation

Either way, it should have a good chance of success.
. . . Gary
GaryRouth is offline   Reply With Quote
Old 07-12-2003, 03:32 PM   #6
Member (14 bit)
Premium Member
 
TwoRails's Avatar
 
Join Date: Jan 2002
Location: The Great NorthWest
Posts: 12,594
Path=C:\Windows;C:\Windows\Command;C:\;C:\CDROM;C:\BRCD\BIN;C:\BRCD\COMMAND
Path=C:\Program Files\Executive oftware\DiskeeperWorkstation
~~~~~~~~~~~`
If I remember right, the second liine would have to read:

SET PATH=%PATH%;Path=C:\Program Files\Executive oftware\DiskeeperWorkstation

Otherwise, PATH, would just be set to the second line. You can also, for testing purposes, add the "Pause" command so that you can narrow down the offending line, like:

Pause
Path=C:\Windows;C:\Windows\Command;C:\;C:\CDROM;C:\BRCD\BIN;C:\BRCD\COMMAND
Pause
SET PATH=%PATH%;Path=C:\Program Files\Executive oftware\DiskeeperWorkstation
Pause

That way you will pause before, during, and after the PATH commands.

HTH

TwoRails
TwoRails is offline   Reply With Quote
Old 07-13-2003, 12:17 PM   #7
Member (8 bit)
 
plumerjr's Avatar
 
Join Date: Nov 2002
Location: Providence,RI
Posts: 156
Send a message via Yahoo to plumerjr
How do I edit it. I opened it up through notepad. Is ok to edit with notepad or is there a special way to do it ?
plumerjr is offline   Reply With Quote
Old 07-13-2003, 12:25 PM   #8
Member (14 bit)
Premium Member
 
TwoRails's Avatar
 
Join Date: Jan 2002
Location: The Great NorthWest
Posts: 12,594
Any text editor will work. And, word processors that can save files as text will also work. I haven't used Notepad in many years (I've always used a "replacement" proggy) but if I remember right, it is a text editor so you should be fine.

Copy your original file for a "just-n-case," though. It's also always nice to have a copy so you can "remember" what commands were in there.

Also, you can put the Pause command in as many times as you like for debugging! You can remove them after things are running fine.

HTH

TwoRails
TwoRails is offline   Reply With Quote
Old 07-13-2003, 01:17 PM   #9
Member (8 bit)
 
plumerjr's Avatar
 
Join Date: Nov 2002
Location: Providence,RI
Posts: 156
Send a message via Yahoo to plumerjr
I forgot all about the "msconfig"system configuration utility. Had a brain cramp I guess, lol. I'll be sure to make a copy for "just-in-case". Thanks for the help I'll let you know how it works.
plumerjr is offline   Reply With Quote
Reply

Bookmarks

Still Need Help? Type Your Keywords Here:


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

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 On
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 11:46 PM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2012, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 PL2