XPost: microsoft.public.windowsxp.general, atl.msdos.batch.nt   
   From: NONONOmisc07@bigfoot.com   
      
   In microsoft.public.windowsxp.general, on Sun, 27 Sep 2015 00:36:07   
   +0100, "J. P. Gilliver (John)"  wrote:   
      
   >In message , micky   
   > writes:   
   >>In microsoft.public.windowsxp.general, on Sat, 26 Sep 2015 12:05:15   
   >>+0100, "J. P. Gilliver (John)"  wrote:   
   >[]   
   >>>>>Does this remember if you select true character mode, with Alt-Enter?   
   >>   
   >>Sorry.  I misread your question and answered as if you had asked about   
   >>Alt-Space.    I also don't know the term  true character mode.   
   >   
   >Not surprising, as I made it up;   
      
   Well then, I'm glad I commented.   I almost didn't, thinking  Why should   
   one comment on something he doesn't know?   
      
   > I'm not sure what the "official" name   
   >for that mode is, if there is one. I called it that because, on some   
   >systems at least, I think it actually changes the mode of the graphics   
   >hardware, to an 80 by 25 character mode that's there from days long ago.   
   >[]   
   >>Right.  It's not a box, but the full screen.   In my XP system, however,   
   >>the characters were a bit fuzzy and maybe wider, giving less on the   
   >   
   >Unless it's a laptop, that's probably your monitor: some modern   
      
   It's a Viewsonic thin screen monitor, and until I get back to XP I can't   
   try it with anythihng else, including the Dell Trinitron CRT I'm using   
   now.,   
      
   >(especially non-CRT) monitors won't even display this old mode - the   
      
   Yeah, non-CRT.   
      
   >ones that do aren't optimised for it. (Pressing the auto-adjust button -   
   >or manually tweaking the monitor - might make it less fuzzy. But then   
   >you'd have to redo that when you got back into graphics mode, so don't   
   >bother.)   
   >[]   
   >>Last Sunday my XP system failed.  I spent a lot of Monday trying to   
   >>repair it (another thread I hope to start) and Monday night  I moved to   
   >>my only spare computer that had a HDD and an OS.  A friend who upgraded   
   >>his office gave me a Dell Vista computer,   
   >>   
   >>and now in Vista when I try to do Alt-Enter, I get  "This system does   
   >>not support fullscreen mode".   This is with Start | run | cmd or a   
   >>shortcut that calls tcc/le.  (I have no bat files except autoexec.bat   
   >>which doesn't pause in the middle, and whose box disappears right away)   
   >   
   >I _think_ that's how .bat files have run in the Windows environment   
   >since '95 - when they've finished, their command window closes. But if   
      
   Yeah, that's fine.  I just meant that because of that, I can't adjust   
   the size of the screen or try alt-enter.   
      
   >you run them from an already-opened command prompt, e. g. by typing   
   >   
   >\autoexec   
   >   
   >at the command prompt, they _won't_ disappear when they finish (or   
   >rather the command window won't).   
      
   Right, but to go back a ways, I'll have to wait until I have a bat file   
   with a pause of some sort in it, to adjust the width a window opened by   
   clicking on a bat file, and then to see if the new value lasts from one   
   windows session to another.   A lot of other things to do first**, (like   
   copying over my Firefox history and password files.   And the cookies   
   from a web order I was assembling.)   
      
   **Well, I get impatient.   I put a "pause" in autoexec.bat (which had   
   only one line it it before) and set the screen width to 126 and now the   
   cmd window is the same width as the screen.   I'll check after rebooting   
   if it has stayed that way.   
      
   >>If only we could have a format with the best of all 3 possible formats!   
   >>(JK, I'm pretty much satisfied, at least if it remembers the width in   
   >>the next windows session.)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)