PBDOS vs. Win XP

[steve robinson]

I can't believe that I am the only person in the world who cannot make PBDOS (3.0 or 3.5, haven't tried TB1.1 yet) work with Win XP Pro, but maybe I am! Can anybody help me?

As long as the program stays in SCREEN 0 everything is fine, but using SCREEN 12, as most programs do, completely clobbers the font and color settings of both the IDE and the command prompt screen, usually ending up with blinking text at the command prompt! That is, the program runs fine either from the IDE or exe file, but after running it you no longer have a very readable screen. As expected, the problem does not occur under Win98 or WinME.

Typical code:

'PBDOSTST.BAS- TEST OF PBDOS UNDER WINXP
DEFINT I-N : CLS : COLOR 10
INPUT"RUN SCREEN 12 TEST (Y/N)";Q$
IF Q$="Y" OR Q$="y" THEN
SCREEN 12 : WINDOW(0,0)-(639,479)
CIRCLE(300,225),75,12
DO WHILE INKEY$="" : LOOP
SCREEN 0 : COLOR 10
END IF

PRINT"SCREEN 0 TEST "
FOR I=0 TO 5 : PRINT USING"#.#### ";RND; : NEXT
DO WHILE INKEY$="" : LOOP
END

[Matthew Berg]

Do you run the application in full-screen or windowed mode?

------------------
If you try to make something idiot-proof, someone will invent a better idiot.

[steve robinson]

Originally posted by Matthew Berg:
Do you run the application in full-screen or windowed mode?

Good question! The Command Line Properties are set to
"Window". PB.EXE comes up in a window. The snippet runs in a windo through
the INPUT statement. Once in SCREEN 12, however, the view is full screen! The full screen
view continues even when I get back to the IDE.

Likewise when I run the exe file it starts out in a window and ends up in full screen once
SCREEN 12 is invoked.

While waiting to hear if this makes sense to you I'll try setting the command line properties
to "full screen".

Thanks, steve robinson



------------------