The program comes up in full screen with black background and white text
characters/drawings.
My eys are getting old and tired and I would prefer black text on white
background. Besides, I prefer doing screen captures of screen output and
insert them into word. Saves a lot of paper. With reverse video, I can
save toner to...
My standard wkst. have winxp. Have tried with:
\GRAPHICS /R \PRINTER.PRO /PRINTBOX:A22
but that are not suffisient.
Creating a pif and loading ansi.sys does not help to.
Anyone know what to do? If the solution also works in win9x, it would be
great.
In newsan.2005.03.25.19.49.04.662070@swipnet.se,
Rickard B Hansson <r.b.h@swipnet.se> hunted and pecked:
> Hi.
>
> I have an old dos program that starts with following bat-file:
>
> \GRAPHICS HPDEFAULT \PRINTER.PRO /PRINTBOX:A22
> \program.EXE
>
> The program comes up in full screen with black background and white
> text characters/drawings.
>
> My eys are getting old and tired and I would prefer black text on
> white background. Besides, I prefer doing screen captures of screen
> output and insert them into word. Saves a lot of paper. With reverse
> video, I can save toner to...
>
> My standard wkst. have winxp. Have tried with:
> \GRAPHICS /R \PRINTER.PRO /PRINTBOX:A22
> but that are not suffisient.
>
> Creating a pif and loading ansi.sys does not help to.
>
> Anyone know what to do? If the solution also works in win9x, it would
> be great.
>
> //regards rbh
Archived from groups: microsoft.public.windowsxp.customize,microsoft.public.basic.dos (More info?)
On Fri, 25 Mar 2005, Rickard B Hansson wrote:
> Hi.
>
> I have an old dos program that starts with following bat-file:
>
> \GRAPHICS HPDEFAULT \PRINTER.PRO /PRINTBOX:A22
> \program.EXE
>
> The program comes up in full screen with black background and white text
> characters/drawings.
>
> My eys are getting old and tired and I would prefer black text on white
> background. Besides, I prefer doing screen captures of screen output and
> insert them into word. Saves a lot of paper. With reverse video, I can
> save toner to...
>
> My standard wkst. have winxp. Have tried with:
> \GRAPHICS /R \PRINTER.PRO /PRINTBOX:A22
> but that are not suffisient.
>
> Creating a pif and loading ansi.sys does not help to.
>
> Anyone know what to do? If the solution also works in win9x, it would be
> great.
Perhaps you could load a new VGA palette with black and white exchanged
in the palette.
The FPMAN220 package mentioned on my Computer Tips page[1] includes both a
VGA font editor (fontman) and a palette editor (palman). The vga.com
program can load fonts,
vga font myfont.fnt
or palettes,
vga pal mypal.pal
or both,
vga font c:\utils\CTL1252.FNT pal c:\utils\bright.pal
(an actual example from one of my batch files).
Try creating a palette with black and white exchanged, load that palette,
and see if that works for you.
[1] "Nineteenth Tip: ISO-8859-1 and CP1252 fonts for DOS, DOS-boxes, and
Terminal or HyperTerminal. Bonus: Lumber Cartel Sooper Sekrit Decoder
Ring (TINLCSSDR)."
http://www.chebucto.ns.ca/~af380/Tips.html#Tip019 --
">> consider moving away from Front Page...."
">To what? Any suggestions?"
"Naked bungee-jumping. It's less humiliating <g>"
-- Matt Probert in alt.www.webmaster, March 20, 2005
Archived from groups: microsoft.public.windowsxp.customize,microsoft.public.basic.dos (More info?)
On Sat, 26 Mar 2005, Rickard B Hansson wrote:
> On Sat, 26 Mar 2005 09:26:25 -0400, Norman L. DeForest wrote:
>
> >> The program comes up in full screen with black background and white text
> >> characters/drawings.
>
> >> My eys are getting old and tired and I would prefer black text on white
> >> background.
>
> > Perhaps you could load a new VGA palette with black and white exchanged
> > in the palette.
>
> > The FPMAN220 package
>
> Seems like the colours are hard coded. The program was originaley written
> for zx81 in -81...
>
> After the porting to ibm pc, the author has dropped development.
>
> Think I have to live with the dark screen.
Is the program still available? Is there a location where it can be
downloaded? Some experimentation might find something -- such as a patch
to change the default colours.
--
">> consider moving away from Front Page...."
">To what? Any suggestions?"
"Naked bungee-jumping. It's less humiliating <g>"
-- Matt Probert in alt.www.webmaster, March 20, 2005
Archived from groups: microsoft.public.windowsxp.customize,microsoft.public.basic.dos (More info?)
"Rickard B Hansson" <r.b.h@swipnet.se> wrote in message
newsan.2005.03.25.19.49.04.662070@swipnet.se...
> Hi.
>
> I have an old dos program that starts with following bat-file:
>
> \GRAPHICS HPDEFAULT \PRINTER.PRO /PRINTBOX:A22
> \program.EXE
>
> The program comes up in full screen with black background and white text
> characters/drawings.
>
> My eys are getting old and tired and I would prefer black text on white
> background. Besides, I prefer doing screen captures of screen output and
> insert them into word. Saves a lot of paper. With reverse video, I can
> save toner to...
>
> My standard wkst. have winxp. Have tried with:
> \GRAPHICS /R \PRINTER.PRO /PRINTBOX:A22
> but that are not suffisient.
>
> Creating a pif and loading ansi.sys does not help to.
>
> Anyone know what to do? If the solution also works in win9x, it would be
> great.
AFAIK, GRAPHICS.COM is for printing only. If you already tried using ANSI
with reverse video enabled, then the program is hard coded to screen output.
Either way, I don't see how this affects your ability to capture the text
into Word. AFAIK, the copy/paste function copies raw text regardless of any
colors displayed. If you are copying the screen as a graphic (Alt+PrtScrn),
you can easily paste it into MsPaint (or other graphic editor) and invert
(reverse) colors before printing.
BTW, microsoft.public.basic.dos is for discussions regarding the programming
language BASIC for DOS, not general DOS related discussions. HTH.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.