nathan
Guest
|
Post by nathan on Aug 15, 2018 13:54:27 GMT 1
So i just started playing around with this program because we will be switching to 64bit soon, and wanted to get this working.
i am trying to run foxpro on a pc, and the database is on a networked server.
the directories are as follows: c:nevans this is the main folder on the employee pc \\pc8\c ----mapped to z:\evans this is the networked drive with the database files in it
here is my autoexec file at the moment.
USE Z: Z:\EVANS
USE D: C:\NEVANS\
D:
CALL FOXPROL.EXE
Z:
so when i open vdos, it opens foxpro, and when i select customer, it brings an error up saying "file cust does not exist" referring to the cust.dbs file
am i doing something wrong? For some reason it is not seeing the mapped network drive z:\evans and using the database files
any help would be appreciated, thanks!
|
|
|
Post by Jos on Aug 15, 2018 14:18:59 GMT 1
The directory structure in vDos could not match with what you’ve on the current system. In vDos it is (DOS letters on the left, Windows on the right): C: -> C:\vDos (if you selected the default installation directory) D: -> C:\NEVANS\ Z: -> Z:\EVANS\
But you also have “CALL FOXPROL.EXE”, while CALL is to run another batch file (FOXPROL.BAT?). The last “Z:” is redundant if this is the last command in autoexec.txt. Also USE Z: Z:\EVANS seems questionable. So I suggest you put this in autoexec.txt: USE Z: \\pc8\c\EVANS\ USE D: C:\NEVANS\ D: FOXPROL.EXE (or CALL FOXPROL.BAT)
If it still doesn’t work, start vDos with the /log option (“…vDos.exe” /log). The generated vdos.log file will show you why cust.dbs couldn’t be opened/found.
Jos
|
|
nathan
Guest
|
Post by nathan on Aug 15, 2018 17:02:08 GMT 1
here is the log file with the new settings.
vDos 2018.05.01 0.06 C: => (Local) C:\vDos\ Z: => (Remote) \\pc8\c\EVANS\ D: => (Local) C:\NEVANS\
Execute: FOXPROL.EXE 0.07 Record locking verified for DOS D: Int 21 unhandled call EA00 Int 2F unhandled call 1600 FindFirst failed: D:DEFAULT.FKY(18) FindFirst failed: D:\DEFAULT.FKY(18) FindFirst failed: D:\FOXDOC.EXE(18) FindFirst failed: D:\FOXGRAPH.EXE(18) FindFirst failed: D:\GENSCRN.EXE(18) FindFirst failed: D:\GENSCRN.APP(18) FindFirst failed: D:\GENSCRN.FXP(18) FindFirst failed: D:\GENSCRN.PRG(18) FindFirst failed: D:\GENMENU.EXE(18) FindFirst failed: D:\GENMENU.APP(18) FindFirst failed: D:\GENMENU.FXP(18) FindFirst failed: D:\GENMENU.PRG(18) FindFirst failed: D:\GENGRAPH.EXE(18) FindFirst failed: D:\GENGRAPH.APP(18) FindFirst failed: D:\GENGRAPH.FXP(18) FindFirst failed: D:\GENGRAPH.PRG(18) FindFirst failed: D:\GENXTAB.EXE(18) FindFirst failed: D:\GENXTAB.APP(18) FindFirst failed: D:\GENXTAB.FXP(18) FindFirst failed: D:\GENXTAB.PRG(18) FindFirst failed: D:\GENPD.EXE(18) FindFirst failed: D:\GENPD.APP(18) FindFirst failed: D:\GENPD.FXP(18) FindFirst failed: D:\GENPD.PRG(18) OpenFile failed: 50307967.TMP(2) => C:\NEVANS\50307967.TMP OpenFile failed: 50307904.TMP(2) => C:\NEVANS\50307904.TMP 0.09 FindFirst failed: D:\FOXHELP.DBF(18) Int 2F unhandled call AD80 FindFirst failed: D:MENU.EXE(18) OpenFile failed: MENU.EXE(2) => C:\NEVANS\MENU.EXE FindFirst failed: D:MENU.APP(18) OpenFile failed: MENU.APP(2) => C:\NEVANS\MENU.APP 0.84 FindFirst failed: D:BEDCI.EXE(18) OpenFile failed: BEDCI.EXE(2) => C:\NEVANS\BEDCI.EXE FindFirst failed: D:BEDCI.APP(18) OpenFile failed: BEDCI.APP(2) => C:\NEVANS\BEDCI.APP OpenFile failed: CUST.DBF(2) => C:\NEVANS\CUST.DBF OpenFile failed: EVANS\CUST.DBF(2) => \\pc8\c\EVANS\EVANS\CUST.DBF 0.85 FindFirst failed: C:\NEVANS\BEDCI.PRG(3) FindFirst failed: Z:\EVANS\NEVANS\BEDCI.PRG(3) 1.07 Delayed logging, set w/o DOS call: Int 22 => f000:0003 Int 24 => 2183:2206 1.24 Idle 1.70 Idle end 2.05 OpenFile failed: 50307907.TMP(2) => C:\NEVANS\50307907.TMP 2.77 OpenFile failed: 50310268.TMP(2) => C:\NEVANS\50310268.TMP 4.11 Delayed logging, set w/o DOS call: Int 24 => original 4.83 vDos ended by EXIT (0)
|
|
nathan
Guest
|
Post by nathan on Aug 15, 2018 17:05:17 GMT 1
fixed it! at the end of the log: OpenFile failed: EVANS\CUST.DBF(2) => \\pc8\c\EVANS\EVANS\CUST.DBF i changed the dir to just \\pc8\c\ it was trying to go to the evans folder twice!
thank you for your help!
|
|
|
Post by Jos on Aug 15, 2018 19:30:37 GMT 1
pc8 seems to be a regular Windows PC. If it is also used by someone, consider to replace it by a fileserver. A low-priced NAS (Synology DS118…) would already do better since it is dedicated to service network requests, not troubled by an user running programs and perhaps doing unexpected things.
Jos
|
|
nathan
Guest
|
Post by nathan on Aug 15, 2018 21:14:23 GMT 1
PC8 IS USED strictly as a server, it is strictly used to host database files for all other pcs and also pictures and backups. nobody but me touches that PC!
also, i got dosprn to work with vdos plus, stupid me didnt think to go to dosprn website, they have the command string there for vdos and vdos plus.
|
|
|
Post by Jos on Aug 15, 2018 21:46:42 GMT 1
A dedicated fileserver like a NAS would still be a better option for various reasons (speed, reliability, maintenance…). I hope you at least backup the hosted files of that PC, preferably on two different media, of which one is always for some time disconnected.
Jos
|
|