Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

invalid setting

Posted on 1998-10-24
12
Medium Priority
?
253 Views
Last Modified: 2010-04-27
When my computer boots I get this message"Invalid setting MSDOS Sys File  ORIG-DIAG-BOOTMENU=<NIL> and when I run scandisk in DOS I get this message "scandisk detected an invalid long filename entry  on this drive but was unable to fix it" How do I fix these problems and are they related?
0
Comment
Question by:olsonl
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
12 Comments
 
LVL 1

Expert Comment

by:jacobas
ID: 1011737
yes they are- rem out the DOS Sys file and then try.  I think that file is unnecessary anyway!
0
 

Author Comment

by:olsonl
ID: 1011738
How do I do that?
0
 
LVL 1

Expert Comment

by:MacDuffie
ID: 1011739
Open your msdos.sys file with notepad, copy and post it here.
Patty
0
Take our survey for a chance to win!

As a valued customer of Targus, we’d like to ask you a few questions about us. As thanks, you will be automatically entered for a chance to win a $500 VISA gift card. To enter, just complete the survey by September 15, 2017.

 
LVL 2

Expert Comment

by:pjmaze
ID: 1011740
To solve the first problem i need to see your msdos.sys file, the second problem has something to do with directory size. The problem is that MSDOS only recognizes 64 chars to be a valid path
( i assume that you use Win 95 )

Send the Msdos.sys !

See ya

0
 

Author Comment

by:olsonl
ID: 1011741
win 98
0
 

Author Comment

by:olsonl
ID: 1011742
I have fixed the problem, thanks anyway
0
 
LVL 1

Expert Comment

by:jimat
ID: 1011743
You should award the points or delete the question. :-)
0
 

Expert Comment

by:kevcraig
ID: 1011744
at the command prompt type edit edit msdos.sys find the invalid line and delete it. This will eliminate the error.
0
 

Author Comment

by:olsonl
ID: 1011745
I would delete but There is nowhere to delete it.
0
 

Author Comment

by:olsonl
ID: 1011746
DELETE DELETE DELETE DELETE
0
 

Accepted Solution

by:
hlava earned 100 total points
ID: 1011747
try find program Norton Disk Doctor for Win 95 and run it may be it can help you.
0
 

Expert Comment

by:hlava
ID: 1011748
HEY I HAVE SAME PROBLEM

try add some lines
MSDOS.SYS must have over 1024 kb

the end of MSDOS.SYS look like this:

;The following lines are required for compatibility with other programs.
;Do not remove them (MSDOS.SYS needs to be >1024 bytes).
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxA
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxB
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxC
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxD
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxE
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxF
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxG
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxH
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxI
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxJ
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxK
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxL
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxM
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxN
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxO
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxP
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxQ
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxR
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxS
;Do not edit this file without prior knowledge!



GOOD LUCK
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Backups and Disaster RecoveryIn this post, we’ll look at strategies for backups and disaster recovery.
If you're a modern-day technology professional, you may be wondering if certifications are really necessary. They are. Here's why.
Video by: ITPro.TV
In this episode Don builds upon the troubleshooting techniques by demonstrating how to properly monitor a vSphere deployment to detect problems before they occur. He begins the show using tools found within the vSphere suite as ends the show demonst…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question