Setting up Vision

[mark pruitt]

I recently dusted off an old Compaq laptop, put OpenDOS 7.03 on it and
installed PB/DOS 3.5. I remembered I had Vision, so I installed it as well.
I followed all of the directions in the readme.doc for setting up
directories in the compiler directory list and adding to the path statement
in the autoexec.bat file. I still get error 493 Compiler not found when I
try to execute any of the code (been using the tutorials and examples).
Usually, "windows.bi" is the line high lighted.

Any help getting this to work right is greatly appreciated. Thanks.

------------------

[Mel Bishop]

Recommend making sure your PATH statement in your AUTOEXEC.BAT
file includes the compiler sub-directorie(s). I am not familiar
with OpenDOS x.x but see if it has the equivalent of the old DOS
APPEND. Append lets programs find their support files and the
syntax is identical to the PATH statement.


------------------

[mark pruitt]

Thanks Mel. OpenDOS does have an append statement, but 1) it didn't
make a difference and 2) the developer recommends you don't use it.

I modified autoexec.bat to include the /vision/lib, /vision/include,
and /workshop paths, but it still gives the compiler error. I tried
it on another machine (Windows ME) with the same results. If I have
to, I'll change the path for all of the include and link statements,
but according to the readme.doc, you shouldn't have to do that.

------------------

[Lance Edmonds]

If you are compiling from the IDE, you should add those paths to the Options|Directories table in the IDE. Don't forget that you can specify multiple paths in each field by using a semi-colon to separate them, thus:

C:\VISION\INCLUDE;.;C:\PROJECTS
...etc

BTW, using a period infers the current directory.

------------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>

[mark pruitt]

Just double checked, but I did that. I followed the instructions
in the readme.doc word for word. When I get some time, I'll play
around with it again.


------------------

[Mel Bishop]

Was the 2nd machine you tried it on also a Compaq? If so, try it
on a non-Compaq machine. Other threads in this web site have
indicated that Compaq machines are not as IBM compatable as the
mfgr would like you to believe.


------------------


[This message has been edited by Mel Bishop (edited April 23, 2002).]

[Gary Stout]

One thing that might be being overlooked is depending on which version
of PB Vision you have. Unless you have version 2.1, it won't work
with PB 3.5. PB Vision 2.0< would only work with PB3.2 or less.

Hope this helps,
Gary Stout

------------------

[mark pruitt]

Gary, I'll have to check on that. I never would have thought of that
possibility. I know for sure I've got PB/DOS 3.5, but I can't say for
sure what version Vision is.

Mel, the other machine is a Compaq desktop. I'll have to find another
machine to try it on.


------------------

[Lance Edmonds]

If the PBL, OBJ, and/or PBU files were compiled for the wrong PB/DOS version, you'd most likely get an Error 507 (Invalid $LINK file) rather than 493.

Therefore, I'd suspect the problem is that files simple cannot be located or opened.

If these "backup" files came from a CDR, did you remove the READ-ONLY attribute from the files after restoring them, and before compiling?

------------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>

[Roy Scott]

you need the \vision\include in the source directory of pb35
options and \vision\lib in the link directory option.

------------------
Roy Scott
http://www.royscott.net

[Roy Scott]

By the way, have you seen the great $20 price on PBVision which
includes PBWorkshop for the latest version?


------------------
Roy Scott
http://www.royscott.net

[Warren Henderson]

One thing that might be being overlooked is depending on which version
of PB Vision you have. Unless you have version 2.1, it won't work
with PB 3.5. PB Vision 2.0< would only work with PB3.2 or less.

Hope this helps,
Gary Stout

------------------

<sigh> Well this keeps me from thinking I am out of my mind at least, I missed that there was an update seeing as I have V2.0 from DSE. Looking at my last setup (new computer made me reinstall) it explains why I had version 1 & PB35 and version 2 and PB32 <shrug>. At least it is only $20 bucks to fix.

Warren

[Warren Henderson]

Or maybe not, it is listed on the current versions but I don't see it (PBvision) on the order form. Grrr old interface new compiler or new interface older compiler.

[Arthur Gomide]

Ask [email protected]

[Warren Henderson]

Channeling your inner scarecrow

In the Wizard of Oz sense, I do have version 2.1 I just wasn't reading the whole label so I thought it was PBDOS 2.1. "If I only had a brain.."

Anone know how big a difference 2.11 makes?

Thanks
Warren