Article View: comp.lang.basic.misc
Article #115Re: Qbasic, XP, parallel port
From: Harry Chickpea
Date: Fri, 05 Mar 2004 16:02
Date: Fri, 05 Mar 2004 16:02
41 lines
3194 bytes
3194 bytes
"Rod Speed" <rod_speed@yahoo.com> wrote: > >Fritz Oppliger <fritzo_two_@direcway.com> wrote > >> What is the magic needed to make qbasic >> talk to the parallel port on WinXP ? > >http://www.lvr.com/parport.htm > >> (how did Microsoft manage to break THAT?) > >By not allowing apps to do anything they like to the hardware directly. > >What any solid OS does. Uhh, make that any solid _multi-tasking_ OS. The requirement isn't there in simple dos sytems and embedded controllers. The real issue is more one of changing standards than direct control. MS _could_ have included ways for transparent control through the OS that still protected the OS, but it was simpler, cheaper, and in their financial best interest not to do so. MS has been trying to kill off DOS apps and force users into MS apps or Visual Studio designed apps for years. Some of the changes of standards are subtle and I wonder if they are designed to trip up older programs. Killing off support for LPRINT was an obvious way that basic programs were affected in the port over to NTVDM, but I've also found that copying a file to the parallel port using the copy command can be a problem as well. In the past, I've been able to print null strings to send a LF CR to printers. Now, I find that unless there is another character (such as a space) seperating each instance of LF CR, XP will sometimes (but not always) return a device fault error. I submit that this is either intentional to encourage use of the print manager or an error in the OS that is unprofessional and unworthy of any OS. I won't even go into the issues that can occur when running a DOS based app in full screen mode instead of windowed mode. One of the most powerful aspects of DOS was that each instruction was minimally affected by a blanketing layer of OS code that was subject to capricious change. When the OS operates as a middle manager between the low level commands and programs, any program becomes subject to OS management errors as well as any shortcomings of its own. MS banks on this.
Technical Details
Message-ID:
<404a9c46.275708979@News.Individual.NET>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!fu-berlin.de!uni-berlin.de!user-2ivehj9.dialup.mindspring.COM!not-for-mailReferences:
<764380f6c7300e3284ef133d22aa0a0b@news.teranews.com> <40466628.600652512@news.comporium.net> <c27bnb$1prg44$1@ID-151056.news.uni-berlin.de> <c2856u$1kf47p$1@ID-69072.news.uni-berlin.de>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10c949,c6c86b1341e74485 X-Google-Attributes: gid10c949,public X-Google-Thread: 108c83,90340131abbe8312 X-Google-Attributes: gid108c83,public X-Google-ArrivalTime: 2004-03-05 08:02:22 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!fu-berlin.de!uni-berlin.de!user-2ivehj9.dialup.mindspring.COM!not-for-mail From: hchickpeaREMOVEME@hotmail.com (Harry Chickpea) Newsgroups: comp.lang.basic.misc,aus.computers Subject: Re: Qbasic, XP, parallel port Date: Fri, 05 Mar 2004 16:02:36 GMT Lines: 42 Message-ID: <404a9c46.275708979@News.Individual.NET> References: <764380f6c7300e3284ef133d22aa0a0b@news.teranews.com> <40466628.600652512@news.comporium.net> <c27bnb$1prg44$1@ID-151056.news.uni-berlin.de> <c2856u$1kf47p$1@ID-69072.news.uni-berlin.de> NNTP-Posting-Host: user-2ivehj9.dialup.mindspring.com (165.247.70.105) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.uni-berlin.de 1078502541 61132619 I 165.247.70.105 ([183858]) X-Newsreader: Forte Agent 1.5/32.452