 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Forum / Windows 98 / General Topics / April 2004Starup menu "Command Prompt" versus "Safe Mode Command Prompt"
I have my startup menu always enabled with a 30 sec delay. I'm trying to find out what the difference is between "Command Prompt" and "Safe Mode Command prompt". Reason is monitors doing something funky in DOS when using "Command Prompt" that doesn't happen when I choose "Safe Mode Command Prompt" and I'd like to find out what's causing it. >I have my startup menu always enabled with a 30 sec delay. > [quoted text clipped - 4 lines] >that doesn't happen when I choose "Safe Mode Command Prompt" and I'd like to >find out what's causing it. Safe Mode Command Prompt by-passes the autoexec.bat and config.sys files. Check those. Regards, Bill Watt Computer Help and Information http://home.epix.net/~bwatt/ Microsoft, the company that gave us Edlin. ;-) > >I have my startup menu always enabled with a 30 sec delay. > > [quoted text clipped - 13 lines] > Computer Help and Information http://home.epix.net/~bwatt/ > Microsoft, the company that gave us Edlin. ;-) Nope, config.sys is empty, e.g. nothing in it and autoexec.bat only has a path statement in it. I figure it's some "default" something Windows does behind the scene. What funky thing exactly is the monitor doing?  SignatureGlen Ventura, MS MVP W95/98 Systems http://dts-l.org/goodpost.htm > > >I have my startup menu always enabled with a 30 sec delay. > > > [quoted text clipped - 21 lines] > > I figure it's some "default" something Windows does behind the scene. Get the "C:\" prompt and type "dir", acts normal until end of listing and then "poof" it's like the screen is split vertically in two, the right side mirroring the left side accept it's offset by two lines. If I enter "Mode mono" alls well again but the minute I do "Mode co80" it's funky again. Monitor reports same freq. and res etc. used under either "normal" or "Safe mode" command prompt hence why I think it's something under the hood Windows is doing (even though I'd always thought nothing in Windows should have any effect on a "Command Prompt" boot. Also doesn't do it in a DOS session within Windows when run full screen.or if I boot with an EBD floppy. At this point I'd just like to know what's doing it so I don't find myself in the same place if I decide to or have to do a complete re-install.. There's also no signs of anything like a virus etc. (and I've been around enough to sense that) and no anti-virus software etc. indicates anything amiss.. As I'm writing this, I just had a thought to move/rename "C:\Videorom.bin" as it has always seemed out of place and I have no idea what creates it or what it's purpose is. Just something to check out of desperation but given it appears to be a copy of the video cards rom, maybe it's used for "something" and it's corrupt. What's the worst that can happen heh :) What funky thing exactly is the monitor doing? -- Glen Ventura, MS MVP W95/98 Systems http://dts-l.org/goodpost.htm > > On Sun, 18 Apr 2004 22:09:30 -0300, "pjp" > > <pjp_is_located_at_@_hotmail_._com> wrote: [quoted text clipped - 24 lines] > > I figure it's some "default" something Windows does behind the scene. > Get the "C:\" prompt and type "dir", acts normal until end of listing and > then "poof" it's like the screen is split vertically in two, the right side [quoted text clipped - 54 lines] > > > > I figure it's some "default" something Windows does behind the scene. Could it have anything to do with display drivers or video card(try a different one)? Maybe a directX update would help? Other than that I would have to say it sounds like a problem either with the command program or some sort of hidden windows screw up in which case a re-install would be in order. Please let me know if you fix this issue and how so as it is a very interesting problem. Thank you. www.myhelpdesk.org Free Computer Help by email Some ATI cards did this a while back. I'm not sure what the fix was. there should be some reference to them at the video card manufacturers website. you may find that you just can't use dos anymore in a non windows enviroment. The basic dos compatability built into the newer cards today are usually enough to get past the post screen. i'm guessing that there is somethign in the startup process that changes the display resolution or columns being displayed when you start up normally. this might not be a good thing if your video card doesn't supoport it. haver you tried booting from a start uujp floppy and see if the problem is there too? > Get the "C:\" prompt and type "dir", acts normal until end of listing and > then "poof" it's like the screen is split vertically in two, the right side [quoted text clipped - 54 lines] > > > > I figure it's some "default" something Windows does behind the scene. On Sun, 18 Apr 2004 22:09:30 -0300, "pjp" >I have my startup menu always enabled with a 30 sec delay. >I'm trying to find out what the difference is between "Command Prompt" and >"Safe Mode Command prompt". >Reason is monitors doing something funky in DOS when using "Command Prompt" >that doesn't happen when I choose "Safe Mode Command Prompt" and I'd like to >find out what's causing it. If you mean the F8 boot menu (as I'm sure you do) then... "Safe Mode Command Prompt" - skips Config.sys and Autoexec.bat - performs HiMem.sys memory check "Command Prompt" - processes Config.sys and Autoexec.bat - skips HiMem.sys memory check So choose Command Prompt and then before you press Enter, press Shift-F8 so that single-stepping is enabled ("Y"). Then try an N for each prompt until the problem goes away; then you've found your culprit (which I suspect may be a DOS VESA driver or Emm386.exe) >-------------------- ----- ---- --- -- - - - - Running Windows-based av to kill active malware is like striking a match to see if what you are standing in is water or petrol. >-------------------- ----- ---- --- -- - - - - >"Safe Mode Command Prompt" > - skips Config.sys and Autoexec.bat > - performs HiMem.sys memory check Not quite correct. Himem.sys is not loaded when you boot to "Safe Mode Command Prompt". Try booting there and then running Scandisk from the command prompt. It will fail because there is no extended memory driver (himem.sys) loaded. Ron Martell Duncan B.C. Canada SignatureMicrosoft MVP On-Line Help Computer Service http://onlinehelp.bc.ca "The reason computer chips are so small is computers don't eat much." On Tue, 20 Apr 2004 21:03:43 GMT, Ron Martell <ron@onlinehelp.bc.ca> >>"Safe Mode Command Prompt" >> - skips Config.sys and Autoexec.bat >> - performs HiMem.sys memory check >Not quite correct. Himem.sys is not loaded when you boot to "Safe >Mode Command Prompt". Try booting there and then running Scandisk >from the command prompt. It will fail because there is no extended >memory driver (himem.sys) loaded. Ah thanks; well caught! What I said about HiMem.sys is true only for Safe Mode, not Safe Mode Command Prompt Only. >-------------------- ----- ---- --- -- - - - - Running Windows-based av to kill active malware is like striking a match to see if what you are standing in is water or petrol. >-------------------- ----- ---- --- -- - - - - |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.