First - FANTASTIC!! I am dependent on DOS for some quite elaborate ASEASYAS (Think Lotus 123) macro driven programs, plus an old Word processor that I am familiar with that carries years of reference files, none of which are easily transferred to any "superior modern program". So being able to run these old applications on my WIN7 machine with WIN folders etc is so good.
How to select programs? Having to modify the autoexec.txt file every time seems clumsy. Is a command prompt available?
I have not made extensive tests, but I have printed one page of text, and see that control codes normally not printed, are. Also a 12 character line appeared at the top of the page (OBOU176D5B1OH)
I have not yet tried to print a spreadsheet, so there may also be some problems there. Anyway, the purpose of this post is to ring the bell to see if anyone knows about any problems, and possible solutions and work arounds.
Regards: Ian Macmillan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Selecting programs:
You get the command prompt by simply removing the last line: EXIT.
If you want to start more than one DOS program:
Create some folder to hold your DOS programs (you can also use the default vDos folder).
In this folder add for each of your programs a folder where you copy your program and data files to.
Copy the config.txt, autoexec.txt and language.ini files of vDos to each of these folders.
Create shortcuts to vDos.exe and set the working directory to the program folder.
For each program: completely wipe out the autoexec.txt file and add one single line: USE C: ..
Start the shortcut, you’ll get the DOS C:> prompt (C: is the program folder).
Test if you can start the program.
If so, add that command to the autoexec.txt file and a line with EXIT so the vDos window closes when you exit the program.
Eventually you can fine tune some things with the options in the config.txt files.
Printing:
In your program you have to select an Epson … printer for printing.
Could also be PostScript or PCL, but probably your old programs don’t know about these.
Jos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks very much for the info. I devised a batch file that modifies the autoexec.txt files to select the two DOS programs I mostly use. I created a shortcut on the desktop which brings up a cmd window with the selections.
I am running Win7/32 bit home premium, and possibly the batch file might be useful to someone here:
The DOS program folders and the batch file are located in the VDOS folder. An extra autoexec.xxx file has the directory and filename for the alternative autoexec file that is currently autoexec.txt.
@echo off
CLS
:MENU
echo Select program to run
echo Enter 1 for Breeze
echo Enter 2 for Aseasy
echo Enter 3 to exit
ECHO.
SET /P M=Type 1,2 or 3 then press ENTER:
if %M%==1 goto BRZ
if %M%==2 goto ASA
if %M%==3 goto EOF
:BRZ
if exist Autoexec.brz ren autoexec.txt autoexec.asa
if exist autoexec.asa ren autoexec.brz autoexec.txt
vdos
goto menu
:ASA
if exist autoexec.asa ren autoexec.txt autoexec.brz
if exist autoexec.brz ren autoexec.asa autoexec.txt
vdos
goto menu
I am sure this approach can be expanded and refined, but this is early days...
One other thing: The Aseasy spreadsheet produces nice graphs that display very well, but so far I have been unable to plot a graph. I am using a Brother laser (has PCL) as the default Windows printer that seems to do normal print, and which can plot a graph from "real DOS". I hope that someone will know if this is fixable. So far I have had to do a screen dump and process with Paint, which is sorta clumsy. I think graphs were printable with an Epson MX-80 (memories...)
Thanks again for a wonderful program!
Regards: Ian Macmillan
Last edit: Anonymous 2015-06-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Jos,
Im trying to get my dad's dbase apps to run. I have a data folder (c:data\mphs) where all of the programs are stored. I tried CD Data\Mphs in the autoexec file and vdos does nothing. I copied the data folder into the c:vdos directory. What am I doing wrong?
George
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Remove the line with EXIT from autoexec.txt.
EXIT tells vDos to close the window.
So you won’t see what went wrong.
Without EXIT you get the command line prompt and the error message(s) that caused your program not to run.
Jos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Several programs can transform DOS ASCII printer output to Windows printers.
I once did a survey, none even came close to fulfill my requirements, so I started writing my own routines in vDos.
Then I stumbled upon DOSPrinter that I had missed in my survey. It did what (even more) and how I had figured out I had to implement. I dropped my own work instantly and only had to write some lines to interface with DOSPrinter.
I assume you put the commands in the autoexec.txt and added EXIT back in.
You don’t have to use DOSPrinter:
If your application can print to a PCL or PostScript printer, set nothing.
Set LPT1 = DUMMY and let another program monitor and print #LPT1.ASC.
Set LPT1 = <windows command="" or="" program=""> #LPT1.TXT.
Set LPT1 = @<windows program="" started="" hidden=""> #LPT1.TXT.
Where LPT1 can be LPT1 to 9 or COM1 to 9.</windows></windows>
Jos
Last edit: Jos Schaars 2014-08-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
DP26YI /s starts the DataPerfect Testdrive program, the one you saw starting vDos the first time.
It’s just there to test and demonstrate vDos is working after initial installation.
You can delete that line and even the DPTEST folder.
Have a look at the config.txt file, setting the initial window size, frame, printer settings…
If you have more DOS apps to start:
Create a folder for each one, copy the autoexec.txt and config.txt to those folders.
Adjust mainly the autoexec.txt files to start the apps.
Create shortcuts to the vDos executable and set the “Start in” property of it to the folder containing the autoexec.txt and config.txt file.
If you like to support my work, you can click the “Donate” link on the vDos SourceForge pages.
Jos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Jos,
My father loves vdos. We will be deploying W7 using vdos next Saturday...thanks to you :o)
What is the syntax for changing COLORS in the config file ?
COLORS = (208,96,0) OR COLORS=#1040B1 gives "Invalid Parameter" errors.
Thx,
George
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You have to realize that with this option you’re changing the 16 standard text mode screen colors of (v)DOS.
It’s all or nothing, so you always have to supply 16 color combinations, (r,g,b) or #rrggbb whichever you prefer.
If you (or your dad) really don’t like the original DOS colors:
Uncomment the example line (dimmed colors, my favorite).
Let say your dad is a bit color blind and needs green to stand out more.
That’s the third value (the descriptions are in the line above).
It’s (0,152,0): a (r,g,b) combination where the individual values can range from 0 (no) to 255 (full).
So: no Red, 152/255 = 60% Green, no Blue.
To light it up, still being Green: (0,255,0).
Or whatever you want it to be: (0,0,255): bright Blue.
Jos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ps...the colors do really change (with the "COLORS=" copmmand) for that exe prg...I just wanted to avoid the error....it's NO biggie....WE LOVE VDOS !!!!
Thanks for taking time with me.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Jos,
Let me know when I've exhausted my limit on questions..
When my dbaseIV apps experience a record lock in the vDos environment, my app closes and I have to re-open vdos. Is there a command I can place in front of EXIT to prevent app shutdown ?
Normally, in DOS, the app just waits until the record lock is cleared.
Your Thought ?
George
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Perhaps removing EXIT already clarified things by showing an error message of dBase.
Also normally, it’s the app’s responsibility to retry when a record lock fails.
dBase IV seems to distinguish between local and non-local files.
Your data files are located on a network share?
You could have a look at the Localshare setting in dbSetup.
Jos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just tried vDos to help a client run some old programs on Windows 7.
The first program (compiled in Clipper S87) worked fine. Great!
The 2nd program (compiled in Clipper5, linked with Blinker) gave the following error:
vDos - Exception Initial SP value too low.
Any clues?
Thanks
Garry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That’s a strange error to occur.
It’s generated when the initial value of the stack pointer (SP) in the exec header is less than 4.
The SP should be even and a value of 0 or 2 would let it wrap around the stack segment even before the program is started. Further use of the stack would destroy data or code in other segments.
The program does run with Windows 32 or DOS?
Then this test (it came from DOSBox) should be omitted.
Clipper5/Blinker deliberately uses a weird scheme where the SP indeed is supposed to be initialized at say 0xfffe+2 = 0?
If possible, send me a copy of the executable to look into.
BTW, did you have a look at the Harbour alternative?
Jos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had a look at it.
In DOSBox it was only logged as an execpional situation.
I promoted it to raise an exception.
So i removed the test.
Send me your mail address mids my profile and I'll send you a modified copy of vDos.
Jos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Jos,
Amazing software!!! Thank you so much!
I was "fighting" with DOSbox when found vDOS.
Thing is I have the previously reported error "Initial SP value too low" with the XYWrite III program. It runs in DOSbox... dont know what to do. Can provide the executable, it is from around 1988.
THANKS FOR YOUR HELP AND THE GREAT WORK!!
Joaquin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This exception is removed from the next release.
If you can’t wait for that, register on SourceForge and send me a mail. I’ll send you a “pre-release”.
Jos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your quick reply! Unfortunately sourceforge gives me an error when registering!
My email is joaquindeprada at gmail dot com. Thank you VERY MUCH.
Joaquin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
First - FANTASTIC!! I am dependent on DOS for some quite elaborate ASEASYAS (Think Lotus 123) macro driven programs, plus an old Word processor that I am familiar with that carries years of reference files, none of which are easily transferred to any "superior modern program". So being able to run these old applications on my WIN7 machine with WIN folders etc is so good.
How to select programs? Having to modify the autoexec.txt file every time seems clumsy. Is a command prompt available?
I have not made extensive tests, but I have printed one page of text, and see that control codes normally not printed, are. Also a 12 character line appeared at the top of the page (OBOU176D5B1OH)
I have not yet tried to print a spreadsheet, so there may also be some problems there. Anyway, the purpose of this post is to ring the bell to see if anyone knows about any problems, and possible solutions and work arounds.
Regards: Ian Macmillan
Selecting programs:
You get the command prompt by simply removing the last line: EXIT.
If you want to start more than one DOS program:
Create some folder to hold your DOS programs (you can also use the default vDos folder).
In this folder add for each of your programs a folder where you copy your program and data files to.
Copy the config.txt, autoexec.txt and language.ini files of vDos to each of these folders.
Create shortcuts to vDos.exe and set the working directory to the program folder.
For each program: completely wipe out the autoexec.txt file and add one single line: USE C: ..
Start the shortcut, you’ll get the DOS C:> prompt (C: is the program folder).
Test if you can start the program.
If so, add that command to the autoexec.txt file and a line with EXIT so the vDos window closes when you exit the program.
Eventually you can fine tune some things with the options in the config.txt files.
Printing:
In your program you have to select an Epson … printer for printing.
Could also be PostScript or PCL, but probably your old programs don’t know about these.
Jos
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Thanks very much for the info. I devised a batch file that modifies the autoexec.txt files to select the two DOS programs I mostly use. I created a shortcut on the desktop which brings up a cmd window with the selections.
I am running Win7/32 bit home premium, and possibly the batch file might be useful to someone here:
The DOS program folders and the batch file are located in the VDOS folder. An extra autoexec.xxx file has the directory and filename for the alternative autoexec file that is currently autoexec.txt.
@echo off
CLS
:MENU
echo Select program to run
echo Enter 1 for Breeze
echo Enter 2 for Aseasy
echo Enter 3 to exit
ECHO.
SET /P M=Type 1,2 or 3 then press ENTER:
if %M%==1 goto BRZ
if %M%==2 goto ASA
if %M%==3 goto EOF
:BRZ
if exist Autoexec.brz ren autoexec.txt autoexec.asa
if exist autoexec.asa ren autoexec.brz autoexec.txt
vdos
goto menu
:ASA
if exist autoexec.asa ren autoexec.txt autoexec.brz
if exist autoexec.brz ren autoexec.asa autoexec.txt
vdos
goto menu
I am sure this approach can be expanded and refined, but this is early days...
One other thing: The Aseasy spreadsheet produces nice graphs that display very well, but so far I have been unable to plot a graph. I am using a Brother laser (has PCL) as the default Windows printer that seems to do normal print, and which can plot a graph from "real DOS". I hope that someone will know if this is fixable. So far I have had to do a screen dump and process with Paint, which is sorta clumsy. I think graphs were printable with an Epson MX-80 (memories...)
Thanks again for a wonderful program!
Regards: Ian Macmillan
Last edit: Anonymous 2015-06-07
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi Jos,
Im trying to get my dad's dbase apps to run. I have a data folder (c:data\mphs) where all of the programs are stored. I tried CD Data\Mphs in the autoexec file and vdos does nothing. I copied the data folder into the c:vdos directory. What am I doing wrong?
George
Hi George,
Remove the line with EXIT from autoexec.txt.
EXIT tells vDos to close the window.
So you won’t see what went wrong.
Without EXIT you get the command line prompt and the error message(s) that caused your program not to run.
Jos
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
WOW !!!! It worked !!!!!
One more question: Do I have to use DOSPrinter or can I use Winprint ???
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I think DosPrint is great and is printing everything correctly. How can I BUY it ? The link: http://www.geocities.com/dosprint/#Pricing is no good.
How can I buy it ???
Oh, and you, Jos, are a wizard !!! Thank you for doing this and helping us :o)
Several programs can transform DOS ASCII printer output to Windows printers.
I once did a survey, none even came close to fulfill my requirements, so I started writing my own routines in vDos.
Then I stumbled upon DOSPrinter that I had missed in my survey. It did what (even more) and how I had figured out I had to implement. I dropped my own work instantly and only had to write some lines to interface with DOSPrinter.
The links in DOSPrinter.pdf appear to be dropped.
Standard edition: https://www.swreg.org/cgi-bin/s.cgi?s=30417&p=30417-vDos1&q=1&v=4&d=0
Unlimited edition: https://www.swreg.org/cgi-bin/s.cgi?s=30417&p=30417-vDos2&q=1&v=0&d=0
Jos
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I assume you put the commands in the autoexec.txt and added EXIT back in.
You don’t have to use DOSPrinter:
If your application can print to a PCL or PostScript printer, set nothing.
Set LPT1 = DUMMY and let another program monitor and print #LPT1.ASC.
Set LPT1 = <windows command="" or="" program=""> #LPT1.TXT.
Set LPT1 = @<windows program="" started="" hidden=""> #LPT1.TXT.
Where LPT1 can be LPT1 to 9 or COM1 to 9.</windows></windows>
Jos
Last edit: Jos Schaars 2014-08-01
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I did add Exit back in...
I REM'd this one...rem DP26YI /s
This is an A+ solution for my father's business running Dbase4 apps.
If I get a few bucks to send you, where might I send it ? :o)
DP26YI /s starts the DataPerfect Testdrive program, the one you saw starting vDos the first time.
It’s just there to test and demonstrate vDos is working after initial installation.
You can delete that line and even the DPTEST folder.
Have a look at the config.txt file, setting the initial window size, frame, printer settings…
If you have more DOS apps to start:
Create a folder for each one, copy the autoexec.txt and config.txt to those folders.
Adjust mainly the autoexec.txt files to start the apps.
Create shortcuts to the vDos executable and set the “Start in” property of it to the folder containing the autoexec.txt and config.txt file.
If you like to support my work, you can click the “Donate” link on the vDos SourceForge pages.
Jos
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi Jos,
My father loves vdos. We will be deploying W7 using vdos next Saturday...thanks to you :o)
What is the syntax for changing COLORS in the config file ?
COLORS = (208,96,0) OR COLORS=#1040B1 gives "Invalid Parameter" errors.
Thx,
George
Both are wrong.
You have to realize that with this option you’re changing the 16 standard text mode screen colors of (v)DOS.
It’s all or nothing, so you always have to supply 16 color combinations, (r,g,b) or #rrggbb whichever you prefer.
If you (or your dad) really don’t like the original DOS colors:
Uncomment the example line (dimmed colors, my favorite).
Let say your dad is a bit color blind and needs green to stand out more.
That’s the third value (the descriptions are in the line above).
It’s (0,152,0): a (r,g,b) combination where the individual values can range from 0 (no) to 255 (full).
So: no Red, 152/255 = 60% Green, no Blue.
To light it up, still being Green: (0,255,0).
Or whatever you want it to be: (0,0,255): bright Blue.
Jos
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Will do...thx !
ps...the colors do really change (with the "COLORS=" copmmand) for that exe prg...I just wanted to avoid the error....it's NO biggie....WE LOVE VDOS !!!!
Thanks for taking time with me.
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi Jos,
Let me know when I've exhausted my limit on questions..
When my dbaseIV apps experience a record lock in the vDos environment, my app closes and I have to re-open vdos. Is there a command I can place in front of EXIT to prevent app shutdown ?
Normally, in DOS, the app just waits until the record lock is cleared.
Your Thought ?
George
Perhaps removing EXIT already clarified things by showing an error message of dBase.
Also normally, it’s the app’s responsibility to retry when a record lock fails.
dBase IV seems to distinguish between local and non-local files.
Your data files are located on a network share?
You could have a look at the Localshare setting in dbSetup.
Jos
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Just delete the line that says EXIT.
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I just tried vDos to help a client run some old programs on Windows 7.
The first program (compiled in Clipper S87) worked fine. Great!
The 2nd program (compiled in Clipper5, linked with Blinker) gave the following error:
vDos - Exception Initial SP value too low.
Any clues?
Thanks
Garry
That’s a strange error to occur.
It’s generated when the initial value of the stack pointer (SP) in the exec header is less than 4.
The SP should be even and a value of 0 or 2 would let it wrap around the stack segment even before the program is started. Further use of the stack would destroy data or code in other segments.
The program does run with Windows 32 or DOS?
Then this test (it came from DOSBox) should be omitted.
Clipper5/Blinker deliberately uses a weird scheme where the SP indeed is supposed to be initialized at say 0xfffe+2 = 0?
If possible, send me a copy of the executable to look into.
BTW, did you have a look at the Harbour alternative?
Jos
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
The program DOES work in DOSBOX 0.74
I had a look at it.
In DOSBox it was only logged as an execpional situation.
I promoted it to raise an exception.
So i removed the test.
Send me your mail address mids my profile and I'll send you a modified copy of vDos.
Jos
Done - Thank you very much!
Garry
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi Jos,
Amazing software!!! Thank you so much!
I was "fighting" with DOSbox when found vDOS.
Thing is I have the previously reported error "Initial SP value too low" with the XYWrite III program. It runs in DOSbox... dont know what to do. Can provide the executable, it is from around 1988.
THANKS FOR YOUR HELP AND THE GREAT WORK!!
Joaquin
This exception is removed from the next release.
If you can’t wait for that, register on SourceForge and send me a mail. I’ll send you a “pre-release”.
Jos
View and moderate all "General" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Thank you for your quick reply! Unfortunately sourceforge gives me an error when registering!
My email is joaquindeprada at gmail dot com. Thank you VERY MUCH.
Joaquin