|
|
Post by bigbluepropgirl on Apr 7, 2023 18:43:44 GMT 1
Hello - I'm very new to this - DOS skills are rusty! I've downloaded vDos and the test worked. I intend to register formally after I'm confident vDos will help me use my old RBASE database/billing/work order system. Followed the instructions to the best of my ability [or lack thereof].  Copied everything related to RBASE from old computer running NT. It appears to all be in the vDos\RBASE folder - C:\vDos\RBASE, see inserted dir. There was no batch file - start.bat - or any other .bat file. Looks like the old program ran from C:\servicedb\rbase.exe, or it appears it does. Located autoexec.nt and config.nt that was embedded in System 32 folder, hoping that would help; obtained from Properties/Advanced in old computer. Renamed RBASE folder to 'servicedb' to replicate the path currently used. Still nothing.  Please let me know if you can help. Currently I have RBASE running on one very old computer and day-to-day current work on a separate, newer computer running Windows 10 64bit. The old computer is starting to make some very sad, tired noises - would love to have RBASE moved over so I can retire the old girl and use one computer for everything. Looking forward to your reply - thank you so very much! *Liz* |
|
|
|
Post by Jos on Apr 7, 2023 19:48:00 GMT 1
Did you start Rbase by cd servic~1<Enter>rbase<Enter>, or servic~1\rbase<Enter>?
Your second screenshot shows vdos<Enter>, that just starts a new vDos.exe instance.
If Rbase still does’t start, actually start a new vDos.exe instance by vdos/log<Enter>.
Try again in the new vDos window, and have a look at the generated vdos.log file. Probably something is off with the directory references.
Jos
|
|
|
|
Post by bigbluepropgirl on Apr 7, 2023 20:04:47 GMT 1
Did you start Rbase by cd servic~1<Enter>rbase<Enter>, or servic~1\rbase<Enter>? Your second screenshot shows vdos<Enter>, that just starts a new vDos.exe instance. If Rbase still does’t start, actually start a new vDos.exe instance by vdos/log<Enter>. Try again in the new vDos window, and have a look at the generated vdos.log file. Probably something is off with the directory references. Jos I used the following attempts in both screens 'initial test' and in vDos. I am completely missing something somewhere - I'm not even seeing a generated vdos.log file....if I am even doing that correctly.  I used the two at   tempts below. Maybe I am completely missing something for sure. |
|
|
|
Post by Jos on Apr 7, 2023 20:27:48 GMT 1
Change vdos\servicedb\rbase.exe<Enter> to service~1\rbase.exe<Enter>.
Or rename servicedb back to Rbase (and do rbase\rbase.exe<Enter>). I don’t think that directory name really matters.
Jos
|
|
|
|
Post by bigbluepropgirl on Apr 7, 2023 20:30:37 GMT 1
Apologies, I was on the phone while replying and double posted the pix and some text. Thank you for your quick reply! Let me know your thoughts - I'm excited about the possibility of VDos saving the day
|
|
|
|
Post by bigbluepropgirl on Apr 7, 2023 20:33:31 GMT 1
Renamed to rbase - did rbase\rbase.exe and received message "unable to read system file: library.msg"
Thoughts?
|
|
|
|
Post by bigbluepropgirl on Apr 7, 2023 20:38:43 GMT 1
Renamed to rbase - did rbase\rbase.exe and received message "unable to read system file: library.msg" Thoughts? (12.5 KB) |
|
|
|
Post by Jos on Apr 7, 2023 20:46:16 GMT 1
Would imply the library.msg file could not be found by Rbase.
Did you also try cd rbase<Enter> then rbase<Enter>?
Else start a second vDos instance by vdos/log<Enter>. In the new vDos window try it again, and submit the generated vDos.log file.
Jos
|
|
|
|
Post by bigbluepropgirl on Apr 7, 2023 21:02:06 GMT 1
HUZZAH! I will test a few things within and register on Monday. Jos - I cannot tell you how happy you have made me! Hopefully I will not need much else in the way of troubleshooting.
So very much appreciated - have a great weekend.
|
|
|
|
Post by Jos on Apr 7, 2023 21:17:38 GMT 1
Glad you got it working.
Mind, you can use/try vDos as long you need to be confident all works (better than before).
Jos
|
|
|
|
Post by bigbluepropgirl on Apr 11, 2023 18:35:10 GMT 1
Hello, Jos - We are testing it out now, so far all is going well. I may need some guidance after attempting to connect to a printer. I'm not there yet, but it will be soon. Hopefully I will not have to trouble you with more questions!  Thank you, *Liz* |
|
|
|
Post by Jos on Apr 11, 2023 19:32:39 GMT 1
If you still use a DOS (matrix) printer, add this line to config.txt:
LPT1 = SEL:"Windows_printer_name" RAW
Else just see what vDos defaults bring.
The Printing.pdf document should give you further directions.
Jos
|
|
|
|
Post by bigbluepropgirl on Apr 12, 2023 13:03:22 GMT 1
Not a DOS/matrix printer. Looking to connect to Canon ImageClass D1620 via direct USB. There is no network, just one PC. Attempting to load the drivers to the PC this week, then will launch vDos to see how it handles before troubleshooting. I have all Printing.pdf documents in case they are needed. Fingers crossed!
*Liz*
|
|
|
|
Post by bigbluepropgirl on Apr 20, 2023 14:31:26 GMT 1
Hello, Jos -
Wanted to thank you so much for your assistance. vDos is working very well - printing all good. I am about to register now. Very much appreciate all your time!
*Liz*
|
|
|
|
Post by bigbluepropgirl on Apr 20, 2023 14:39:36 GMT 1
Just discovered - User name that is shown in "About" - is Randy. This is an individual who passed away 3 years ago. Can it be changed to my name?
|
|
