Activity for JB
-
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.
-
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.
-
Did u have a chance to get this resolved?
-
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.
-
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 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?
-
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.
-
I did not say that we never print from a4 to a DOS printer. It's just that for this particular report we need to print to PDFCreator so no choice. Thanks again for your help.
-
Thanks for the quick reply. Everything works now.
-
any reason why printdump.exe is visible in windows XP and windows 10 but not in vDos?
-
Thanks for your help. Below is a partial fix. Alpha4v7 uses 2 external files to print to windows. printdump.exe which is used to setup the PTRINFO.A4 printer config file and winagent.exe which is used to print to the windows printer Unfortunately printdump.exe is not visible in vDos and can not be used to generate PTRINFO.A4 but if the file is already there, printing works. Question is why vDos does not recognize printdump.exe as a valid file. It simply does not exist in vDos. It's not visible in...
-
Thanks for your help. Below is a partial fix. Alpha4v7 uses 2 external files to print to windows. printdump.exe which is used to setup the PTRINFO.A4 printer config file and winagent.exe which is used to print to the windows printer Unfortunately printdump.exe is not visible in vDos and can not be used to generate PTRINFO.A4 but if the file is already there, printing works. Question is why vDos does not recognize printdump.exe as a valid file. It simply does not exist in vDos. It's not visible in...
-
Thanks for your help. Below is a partial fix. Alpha4v7 uses 2 external files to print to windows. printdump.exe which is used to setup the PTRINFO.A4 printer config file and winagent.exe which is used to print to the windows printer Unfortunately printdump.exe is not visible in vDos and can not be used to generate PTRINFO.A4 but if the file is already there, printing works. Question is why vDos does not recognize printdump.exe as a valid file. It simply does not exist in vDos. It's not visible in...
-
I don't get a Windows dialog box and no #ptx.asc file. I guess vDos doesn't recognize PDFCreator as a printer driver. It works the way you describe if I select an Epson LQ printer driver in a4v7 which is a DOS printer but not if I select PDFCreator. (windows printer).
-
To duplicate the issue, install PDFCreator. Start a4v7 and setup a printer. Other -> Config -> Printer Config -> Create/edit Printer -> Windows Printer Driver -> PDFCreator Then print to the driver i.e. Print -> Report -> Standard Mode -> Printer -> PDFCreator
-
Yes. Latest version with a4 network enabled. I don't have a LPTx line. The only changes in config.txt are WINKEY = OFF Mouse = ON
-
I am trying to print a report from alpha4v7 to PDFCreator in windows 10. In windows XP we simply select PDFCreator as printer and it works. In vDos it doesn't. Can anyone help on how to set this up? Is there anything special to do in config.txt?
-
I can confirm that Alpha4v7 now runs flawlessly in Windows 10, 64 bit, vDos on our network. Thank you for the great support. I will definitely register this version.
-
I can confirm that Alpha4v7 now runs flawlessly in Windows 10, 64 bit, vDos on our network.
-
Is there any way to resolve this in vDos? Maybe fool a4 to think it's running in XP or something?
-
In windows XP the a4 status screen (F3) shows file sharing mode = shared Network type = Netbios
-
As per the forum, A4V7 requires a Netbios compatile protocol, which includes such types as Netbeui and TCP/IP. Multi-user mode works in Dosbox but it does not lock the records.
-
I don't have access to a 32-bit pc (yet) but I confirmed the issue has to do with multiple users accessing the same SET table. I copied all a4 data to a new directory on the network to make sure my instance of a4 will be the only user trying to open the data set. As a single user a4 opened the table without issues. I then opened the table on another computer first and tried to open it in vDos which failed with the same error "FIle not found or Access denied" I closed the a4 table on the second computer...
-
It's a 64 bit windows 10 pc I can read/write to the network SET tables with Dosbox (no record locking) but not with vDos so maybe vDos handles the write permission differently.
-
I tried it from 2 different computers with windows 10 and get the same result on both. I think it's a Linux server issue, maybe permissions for that folder.
-
I attached the log. Could be a permissions issue on our linux server but that's above my pay grade.
-
Same result if my copy of alpha4 is the only one running on the network. SET files on the network drive can not be opened.
-
to be clear. The problem only happens if I try to run alpha4 on the network. In singke user mode it works fine and the SET table loads. Problem seems to be the file locking.
-
Yes. it continued affter I clicked the About box but then it stalls when a4 tries to load the relational databse SET tables. Yes there are other users running alpha4 on the network from various windows stations. It is a multi-user database and that's how we are using it. I understand you don't actually support alpha4 but I believe (from reading this thread) that you want vDos to be compatible with as many legacy DOS applications as possible and that you do have access to a copy of alpha4. Maybe you...
-
When I click on the vDos pop up box I get an alpha4 error File not found or access denied. I escape and try to open files manually. I can open .DBF files but not .SET files.
-
Just installed the vDos 2017 0801 version and tried it with alpha4v7. It works great if the data files are on the local drive but if the data is on the network it hangs during startup. During the alpha4 startup when it tries to open the database, I see the message vDos 2017.08.01 Network ID: AcmeCorp and username: xxxx Multi - User Version Loading .... and then it hangs
1
