Invalid startup directory, please check your pif

[didrdede]

I know very little about the legacy d-base program
that this user placed on a windows 2003 server but for
some reason when she initiates the pif file this comes up.

any clues

 

[dbMark]

Right-click on the icon, select Properties, then Shortcut. Look at the paths listed there. Verify that they all exist. Does that fix it?

 

[dbMark]

If the application or development program was recently moved, then perhaps a setting there is invalid.

If it is the dBase program itself, look for CONFIG.DB and verify any folders it points to are valid and the user has appropriate rights there.

If it is the dBase application, look for code defining default or specific drives and/or folders and verify any drives or folders it points to are valid and the user has appropriate rights there.

 

[smarkham604]

Maybe this thread is too old, but I recall pif files from the windows 3.1 days. It basically was an inf type of file to define the resources available to the dos program. Once we migrated to Windows 98, and moved the compiled dbase files to an NT server, the pif files were unnecessary. Simply creating a shortcut to the shared resource on the server was enough to define the operating parameters to allow the compiled Dbase IV files to run.