Activity for vDos
-
Deepak Kumar modified a comment on discussion Printing
Thanks Jos for your patience and response for people using dos2usb, please follow these steps instead of using the command in config.txt lpt1 ="LPT1": install a generic txt printer from add printer, and give a name like DOS2USB Printer, install dos2usb software, then do the following changes in config.txt from where you are calling the program. LPT1 = SEL: "DOS2USB Printer" RAW it prints fine without exiting the program and through Dos2usb Software, the software is reasonably priced and can contact...
-
Edward Mendelson modified a comment on discussion OS X
I've put together a complicated (but I hope working) way to run vDos in OS X. It consists of an Applescript launcher that loads a Wineskin "wrapper" for vDos.exe. When you run it the first time, it will create (and requires) a folder named vDosDisk in your home folder in OS X. This folder will be drive C: when vDos opens. Drive X: in vDos will be your OS X desktop. Drive W: in vDos will be the "Windows" directory inside the Wineskin wrapper, which may or may not be useful to you. You will need to...
-
Jos Schaars posted a comment on discussion General
Not selecting or pasting (by mouse click) text in full screen mode is an exception. I probably found that logical since the vDos window occupies the whole screen. But you could have multiple monitors, do Alt+Tab, Alt+Enter, have a RDP session… I’ll have a second look at that, but it won’t be changed until the next version of vDos. So you’ll have to stick with your solution for now. Jos
-
Jim Butterworth posted a comment on discussion General
aah - problem solved - switched from vDosplus to vDos and it works (as you said it would) absolutely perfectly. I did have one problem - being "clever" I set WINDOW=100 and found the mouse wouldn't select the text from the DOS program for the Windows 10 clipboard, though I could paste from the Windows 10 clipboard into the DOS program. Setting WINDOW=95 works perfectly. vDos is great, thank you so much for your time and skill :-)
-
The Are You Sure (Y/N)? message is neither displayed instantly with NTVDM. Your program first tries to produce some fancy warning signal. For this it hooks into the INT 8 interrupt, the servicing routine is a real mess. It uses several counters that would define the length and pitch of the tones to generate. It reads/writes to the PIT, PIC and keyboard controller. vDos doesn’t support that to the hardware level, and the servicing routine is just wasting away millions of instructions before it finally...
-
Darrin Miller posted a comment on discussion General
In our InnSpectre software F2 File Maintenance and than 13 Reservation Recovery we are seeing a long delay (45s) between menu selection and the first Are You Sure (Y/N)? message. On all our current running machines, XP, Vista, etc. the first Are You Sure message shows instantly. I'm not totally sure what all these recovery processes do except clean up and sort the files. Here is the link for the demo software is you don't already have it. https://mrwizardusa-my.sharepoint.com/:f:/g/personal/thewizard_mrwizardusa_net/ElbKbdL81TZHtn_Zg9SyqKABL9fqKnScMPUgDiCOIQpH0A...
-
The home page of vDos.info states: "If you don't already use (still rely on) a DOS application, want to play/experiment with DOS, its command prompt, programs or games: Forget about vDos, it is not meant for you!" So you should already have a working copy of the program somewhere. However, if you installed vDos to C:\vDos: Windows: Create a subdirectory like Install (C:\vDos\Install). Copy the contents of both disks to there (overwritef iles is OK). Start vDos vDos command prompt: use a: c:\vdos\install...
-
Joshua Hanna posted a comment on discussion General
what if i dont have any of said directories? is there a way i can create them without it giving me issues?
-
DOS programs needs no installation. Just copy the directory(ies) from the old to the new PC. That way you also get any settings or data. Jos
-
I am trying to install this Cincinatti Milicron DOS based Program that has a 2 disk setup and no matter what I get this same error: Install Error: Cannot Create Directory Aborting Install. The program itself is actually an EXE file which I find a little ironic, I was wondering if some one can help me figure out how to make this work, so that i can set this up in the Autoexe.txt file so I can just run the program each time from there.
-
This is a forum about vDos, which handles these things differently from vDosPlus. Please ask your question in the vDosPlus forum.
-
Mario Velchev posted a comment on discussion Advanced
and the files mentioned above.
-
Hi, there is no problem when typing any Bulgarian Cyrillic character on the command line. But when I use my software written in Borland Pascal 7.0 some characters are not presented correctly. I’ve attached the autoexec.txt & config.txt files. I’m running VDosPlus on Win 10 Pro 64-bit laptop.
-
No, just that Win+Ctrl+C/V don’t work anymore. See the Readme file for alternatives. Jos
-
ooooh - are you saying that there is no way of pasting from Windows clipboard to DOS programs now?
-
Many DOS users are aged… I missed “ctrl-win-v”; that key combination is taken by Windows itself since the Fall update. So it won't work in previous vDos versions (or vDosPlus). Jos
-
OK thanks for quick reply Jos - I am not that technical I am afraid (78 now) , though I can make Q&A sing nicely. No idea what a Clipper library might be though.
-
For vDosPlus you would have to consult its forum. In general: vDos has a copy/paste buffer of its own, no size limit, and takes care of DOS/Windows character translation. Characters are very gently - one at a time and only if a DOS program accepts/requests input - made available to the DOS program. The BIOS keyboard buffer isn’t even a factor. In the latest vDos version a change was made to accommodate a Clipper library that maintains a keyboard buffer of its own that could overrun (a msihap of that...
-
I know this is an old thread - but it relates to the 15/16 character buffer when I try to paste from the Windows 10 clipboard to Q&A DOS running (otherwise very well) in VDOS plus dated 15/3/2017 Branch=2015.11.01 Build=2017.03.15 Is there a solution to this please, as I use the old Symantec Q&A DOS v5 very heavily.
-
I know this is an old thread - but it relates to the 15/16 character buffer when I try to paste from the Windows 10 clipboard to Q&A DOS running (otherwise very well) in VDOS plus. Is there a solution to this please, as I use the old Symantec Q&A DOS v5 very heavily.
-
Tracking down the origin of such a problem is often like finding a needle in an unstable haystack moving around. Because of user interaction and deviations in the system clock, the moment the problem surfaces is different each run. So first is to stabilize and minimize the haystack; find a good starting point from where there’s at least no user action anymore. Gladly with vDos that is fairly easy; the problem was with the second Esc key. Determine how the program gets that key by logging BIOS Int...
-
The origin of such a problem is often like finding a needle in an unstable haystack moving around. Because of user interaction and deviations in the system clock, the moment the problem surfaces is different each run. So first is to stabilize, fix and minimize the haystack; find a good starting point from where there’s at least no user action anymore. Gladly with vDos that is fairly easy; the problem was with the second Esc key. Determine how the program gets that key by logging BIOS Int 16h keyboard...
-
Best is of course to have just one vDos.exe and its files around. You even don’t need a Windows mapping or vDos USE command. It’s more than you actually asked for: www.vdos.info/faqs.html - Advanced - A portable DOS application. Jos
-
So, if I have my program loaded on a network share and I have everybody mapped to that share in windows (I: -> \share\iscdemo) can I just put my vdos files in my iscdemo folder and have everybody run that vdos.exe or should everybody have their own vdos files?
-
Jos, Great detective work!!! The problem is fixed and we are back on track testing.
-
Could be you’re missing what SCALE=2 (or 1) and TEXT=44x132 (former LINS=44 and COLS=132) actually are about. Though nice to hear an older version of vDos still does the job for you. Jos
-
Robert Patton posted a comment on discussion General
Thanks for the quick response and for your help. Subsequent to submiting my query I clicked another application shortcut - again added rem to EMS,LINS, COLS to clear them plus added rem to FRAME = ON. but then got Config.txt: scale factor too high for screen resolution (my screen is 1600x900) SCALE = 2 I changed to 1 the window content shows only part of the app display even 80x25 when selected in the app shows only part added rem to it - same problem ==================== I have been using vDos version...
-
The first three can be found in the list of “Major/noticeable changes to version 2018.05.01” on the download page. For the “JMP; illegal descriptor type 1” I would need some test environment to reproduce this error. Jos
-
downloaded latest version & installed over older version vDos - initial test seems to work OK existing shortcut to application creates error messages CONFIG.TXT first unresolved item EMS = ON No valid option added rem to EMS, LINS, COLS to clear VDOS - Exception JMP; illegal descriptor type 1 I don't know how to clear this one
-
That had me going for some while. Your executables are EXEPACKed, At first I suspected vDos detection scheme of these files, or handling them. That had me going on wild goose chase. It came down to an exception in handling conditional jumps with 16 bit offsets. For speed vDos maintains a combined CS:IP 32 bit pointer. It added the offset to that pointer, but with 16 bit offsets the CS has to be masked out first; the destination address is wrapped in the CS segment. With the combined CS:IP this can...
-
We are currently testing our reservation software InnSpectre to use with new Windows 10 machines and vDOS. Everything seems to be going fantastic except one one spot. Of course this is a big issue for us. Here is a list of what we are currently doing: For ease in testing I have copied the vDOS.exe, config.txt and autoexec.txt files to my ISCDemo folder. I double click on vDos.exe and then type ah.exe at the command prompt. Press F1 to go to the main menu. Press F3 to go to the Check-in screen. If...
-
The document doesn’t reveal what memory FoxPro exactly needs. It mentions a warning message “Not enough memory for optimization” will be displayed if memory is insufficient for Rushmore to function. So far no one else has reported this to be an issue. I’ll await further reports and then eventually raise XMS memory accordingly. Jos
-
Jiri Holec posted a comment on discussion General
Yes, for now problem only with compiling. I estimate it is missing 4-6MB. I propose to enlarge XMS to 16MB. Low XMS memory = slow run SQL query see: http://www.foxprohistory.org/rushmore.htm Thanks, Jiri
-
NWR posted a comment on discussion General
FYI: See the vDosPlus thread (below) re SORT info. At the bottom of that thread is a URL of several 16b to 64b SORT routines. https://sourceforge.net/p/vdosplus/discussion/general/thread/c71bfa89/
-
I don’t think it has ever been an issue. Pasting your example text just gives the correct results. Do you have some “FONT = -...” setting in config.txt? If your Windows code page is set to 866 or 855, you of course don’t have to use CHCP. Jos
-
I don’t think it has ever been an issue. Pasting your example text just gives the correct results. Do you have some “FONT = -...” setting in config.txt? If your Windows code page is set to 866 or 855, you of course don’t have to use CHCP.
-
I'm using vDOSPlus 2017.08.01 (build 2018.03.01). Some small bulgarian cyrillic letters are not shown correctly (р, с, т, ...,я). !Windows 10 OEMCP=866. Changing it to 855 doesn't help. Please help to solve the issue. Just I've downloaded the 20180501 version of vDOS. Is this issue solved in the recent version of vDOS?
-
The FreeDOS SORT command and Vernon Buerg's SORTF both run in vDos. They're both fairly easy to find online, e.g. http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/sort/
-
“SORT” is an external program. Why would you use DOS SORT.EXE in any non-DOS based Windows version as they have their own SORT programs? And what SORT.EXE does not work in DOSBox. For vDosPlus you’ll have to consult the vDosPlus forum. Jos
-
Harry Ploss posted a comment on discussion General
I have been using DOS SORT for 25 years in my BAT files to PARSE and SORT groups of files. It works in fine in DOS 6.2 , Win 98 and Win 2000. Does not work in DOSBOX or VDOSplus without it I will need to keep a Win 2000 computer. Have not been able to get it to work in Win 10 x32
-
That is quite unexpected since 10 MB is a lot of memory to DOS standards. I suppose you have no memory problem running the project, just with compiling. If so, what would be missing? Jos
-
Jos, please add more XMS memory. Compiling a large project will cause memory to be depleted. See attachments. The previous version VDos worked fine. Jiri
-
Windows Fall Creators Update introduced new global shortcuts like Ctrl+Win+V = “Open shoulder taps”. The Ctrl+Win key combinations didn’t work anymore. So there’s a new scheme for those. Drawback, if you want your program to use the mouse itself, you have to add the Win key. If you don't you can omit the Ctrl key. Jos
-
JB modified a comment on discussion xBase/Clipper
works great if mouse=off but no mouse
-
works great is mouse=off but no mouse
-
but I am running Windows with the above update and have no issues with the previous version. Even today I can copy paste using the mouse in a4 and holding down the Ctrl key without issues if I switch back.
-
You’ll have to thank MS for that with the Windows Fall Creators Update. If you want to copy/paste w/o the Win (even Ctrl) key, you have to set MOUSE=OFF. Jos
-
In the previous version I was able to copy / paste by pressing the Ctrl key and highligthing the area with the left mouse key. This does not work anymore. I now need to press the win+ctrl key to do the same and would like to get the previous functionality back. The weird thing is Ctrl-V works. I don't need win+ctrl-V to paste. It's only the mouse selection that is affected. Copy / Paste worked much better in the previous version.
-
Works. Thanks.
-
If you don’t make them available by a further USE command, other paths are indeed not available to a DOS program. Jos
-
Walt posted a comment on discussion General
OK, I've figured out that I have to have config.txt and autoexec,txt in the "start in" directory. So a vDos shortcut is essentially for a single project directory, different shortcuts for different projects. Once a window is opened I take it no other directories on the computer are available.
-
SourceForge had some troubles lately (again). It seems my initial reply just disappeared. It has been solved; the ESP register wasn’t updated correctly at some moment. The conditions for this to happen are that specific, it should only involve A4V7. Download and install vDosSetup once more, A4V7 should run as expected. Jos
-
Did u have a chance to get this resolved?
-
I neither encountered a FoxProX program in need for more than 4 MB. FoxProX can indeed make use of more than 4/10 MB extended memory. That extra memory is then used for temporary internal data. When that (enlarged) memory pool gets exhausted, FoxProX will start a cleanup procedure. With 10 MB it’s more frequent, reasonably fast, less noticeable. Above 10 MB less frequent, slower, more noticeable (program hickups). All extended memory has to be initialized/’formatted’ by the Phar Lap DOS extender...
-
FoxPro extended version use 16MB and more. Jiri
-
I never came across a program that could actually make use of more than 4 MB. So 10 MB seemed a nice and safe figure. But I could have missed something, what programs do you use that can put more than 10 MB to use, or even need that? Jos
-
George Contreras posted a comment on discussion General
Thanks Jos, Another one I use is XMEM = 63 XMS, because, some of the programs I use need it, now I read it locked at 10MB of both XMS and EMS memory. So there is no way to turn it to 63 anymore?
-
Mark Killingback posted a comment on discussion General
Thanks! Just tried it and it works perfectly for us.
-
I was aware of that. Didn’t think SPOOL would be actually used now there is a TIO= option. Thought about continuing printing (spooling) as long the printer selection dialog was open. But that had some drawbacks. So I settled (at that moment I thought temporary) for Ctrl+S. Only drawback, that won’t work if your program needs Ctrl+S itself, but what are the odds for such a combination? So I let it be (Ctrl+S), to have a further look at it later on. Forgot all about that… So try Ctrl+S, that should...
-
One of the computers running windows 10 in the office has updated itself to the latest feature update. Unfortunately it seems that Microsoft have taken the opportunity to use Win+Ctrl+S to toggle speech recognition with no way to change or turn this off. Obviously this interferes with vDos keys which we use to spool our dos print jobs. Is there any way of changing this key combination?
-
Both directives should work as expected. Check the vDos version (System menu – About…), eventually submit a copy of your config.txt file. Jos
-
Q1: Is there any way to have vDos start with a smaller font? About 4 Win-F11's smaller? Q2: I can't get the window to be 50x80. vDos only opens in 25x80 mode. I set TEXT = 50x80 but no change happens. I also set WINDOW = -50,1:1 which also has no ettect. What am I missing? Thanks
-
No blinking text in vDos, your client would have to do with the bright background color. Jos
-
Jamie101 posted a comment on discussion General
Hello guys! I been trying out vdos for a while now! My client loves it! Is there any possobile way to put a simple switch command to enbale blinking txt mode? My client needs 25 machines networked with vdos! Only if blinking mode is at hand! You see it's a booking system for taxis and they need Blinking txt to show them what is outstanding! There willing to pay or donate!
-
Frameless was mostly ‘used’ by those not knowing the FRAME=ON option, wondering for instance were the system menu was supposed to be. It isn’t the appearance of a standard window. So at cleaning up config.txt of unneeded options, that one also was thrown out the window. Jos
-
Hi Joss, I'm trying the new version but now I cant use the "FRAME = OFF" anymore, is there a way to get it back on track? If I placed it in the new config.txt just keep getting error at vdos start. I've read in the "Major/noticeable changes to version 2018.05.01" that they are gone, does that means forever?
-
Yes. Same thing for me. I can't create or modify a SET with the new version. Works ok with the previous version so at least I can confirm it's a new issue.
-
I already get an error at creating a SET, so I can at least reproduce that. I’ll have a look at what might cause it… Jos
-
The problem only happens if you browse in a SET and the switch to another SET. If you switch between simple databases there is no issue. To duplicate build 2 sets and switch between them after browsing a bit.
-
I uploaded vDosSetup some 8 hours ago, the date of vDos.exe should be May 14. I opened 4 databases again, browsed all with some scrolling, still no error. Could you test with other databases, mine are quite small. Jos
-
I downloaded vDos about 2 hours ago. Did you post the silent updates before or after 2pm European time? Did you first view and browse the database before switching around?
-
I also opened 4 databases, then switched several times between them, but no error. What if you download vDos again, there have been two silent updates since its first release. Jos
-
a4 on network starts ok, opens up all 4 databases choose open database works pressing W to view and switch open database gives the following error when selecting a new database IRET: Illegal descriptor type O Error happens consistently with same operation. Also happens when running a4 from C drive i.e. single user mode.
-
What version of vDos do you use? CHCP sets the code page used by vDos; what ASCII codes translate to what Unicode characters. If you can generate the small omega by Alt+224, it’s correctly defined in the selected code page. It should then also be generated by the dedicated key (combination) on your keyboard, if this is the problem. Jos
-
Evangelos Papadopoulos posted a comment on discussion General
Hi all. i use two standards of greek, . with chcp 1251 (ELOT928, this is the windows standard for greek language) omega works fine both capital and small letters, both at command prompt line and inside my dos software. . with chcp 737 (the older greek language standard for DOS) indeed there is a small problem with small omega, you can bypass it using alt+224, but as far as i can remember this problem existed since DOS, so much before V-DOS. I also can't see any need to use greek at the command prompt...
-
I've had a chance to test this out and it works fine. Awesome! Thanks.
-
It was of course the /e option (don’t use expanded memory) that made the difference. If a program locates its stack segment in expanded memory, and accesses the stack by both the SS register and another segment register, the memory locations could get mixed up. I did a silent update of vDosSetup.exe; it solves this issue (only detected with Btrieve TSR), as a result vDos is a bit slower. Also two other rather exotic issues are fixed. Jos
-
It’s was of course the /e option (don’t use expanded memory) that made the difference. If a program locates its stack segment in expanded memory, and accesses the stack by both the SS register and another segment register, the memory locations could get mixed up. I did a silent update of vDosSetup.exe; it solves this issue (only detected with Btrieve TSR), as a result vDos is a bit slower. Also two other rather exotic issues are fixed. Jos
-
Serial communications in vDos are quite basic; BIOS 14h functions 1-3 are more or less supported and tested, enabling a program to send and receive data. So vDos can do with Windows file functions to communicate with the assigned device (https://msdn.microsoft.com/en-us/library/ff802693.aspx). For most programs this will suffice. At the 'hardware' level, only reading from and writing to the base port (Transmitter Holding Buffer/Receiver Buffer) will be realistic, the rest is just ignored. To support...
-
Federico Navarro posted a comment on discussion General
Jos, thanks for answering and for your support Unfortunately in many cases software is provided "as is", or even own developed software may rely on 3rd party communications library, binary closed source without support, and in those cases vDos users are quite unable to workaround that situation. May Interrupt driven communications being supported on vDos on the near future? Does it depend on the how many people would benefit from it or it is definitely out of scope? I tried vDos /log. PRUF indeed...
-
No option to change that. Copying the program from the old to the new PC is still the simplest since DOS programs don’t need installation. Jos
-
Jacob Hoyles posted a comment on discussion General
Thanks for enlightening me on that Jos. Is there anyway to change the reported disk space?
-
Some (ancient) DOS programs will choke on large reported disk sizes. It also makes no sense to report GB’s or even TB’s to programs that expect MB’s for drive sizes. To play save, vDos just always reports 120 MB of free disk space. It almost seems the installation program is even choking on this 120 MB. You would have the program already installed on another PC. Just transfer its directory (ies) to the new PC. Else try if the installation program will run in DOSBox. Mind that vDos is not really suited...
-
I am trying to install a DOS program to communicate with an old Programmable Logic Controller (PLC). To communicate with this PLC I will need a DOS program installed that will be able communicate through a serial port. My computer does not have a serial port but I have a USB to serial converter. I have the contents of the installation floppy discs on my computer and I have been trying unsuccessfully to install this program in vDos. The problem I run in to is that when I run the installer it encounter...
-
It is btrieve version 5.10a. It's being started with the command line: btrieve /p:4096 /m:64 /f:32 /b:32 It works fine on vDos 2017.08.01 but ont he new version it didn't.
-
Well, that is quite a story, probably better to communicate directly: jas@vdos.info (the “a” should be an ”o”). Problematic with serial communications in vDos are programs that install and rely on their interrupt driven routines. You can check if a program does so by starting vDos with the /log option (“…vLog.exe” /log). If the vDos.log shows “Int 0B => XXXX:XXXX” or “Int 0C => XXXX:XXXX”, it indeed implements these routines, that are then never called in vDos. If those entries are missing, the program...
-
Jos, Thank you for this great software. I am not being able to communicate through the serial COM ports with vDOS. I searched and read a lot of post regarding the subject on this discussion forums and realized there is a problem on this area and that you made several attempts to make it work but haven’t got real devices to test and test people have been keen to participate first but finally desisted. I hope you keep interest (and energies) on this subject and be able to give it another try. I think...
-
It was Btrieve setting its stack to expanded memory (I also meant that, not upper memory); vDos doesn’t expect program code or a stack segment in there. It saves testing where memory is supposed to be (no relocating with a speed gain). A temporary quick and dirty modification/test seemed to do it. I then noticed a CPU exception was raised in both (!) versions, caused by an illegal IRET instruction. That puzzles me, seemingly Btrieve/vDos recovers from that, but can you confirm Btrieve ran fine with...
-
That’s strange; I myself still use only one DOS program, that also uses the Btrieve database manager. I wanted to add the Btrieve version number, started Btrieve on its own. Behold, it stalled also! It is “Btrieve/N Record Manager Version 5.10a”, and works fine with “btrieve /f:40 /b:12 /u:8 /m:48 /e /c /o”. I have to look into why it doesn’t w/o parameters. Will be one (?) missing, and I suspect causing Btrieve to locate its internal stack in upper memory… Jos
-
Hi. I've tried out the new release and run into an issue. In the previous release a program I run works fine but in the new one it just freezes up and never gets back to the command prompt but I can shut vdos down from the close icon in the top right. The program is Btrieve.exe which is a TSR database program. If you need any further info I'm obviously happy to help.
-
Sebastián Segura modified a comment on discussion General
Thanks for the new version. Downloading to test it. Regards, Sebastián Segura
1 >
