CAPI, paths, blind passwords, UE....


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Bob A on July 30, 2013 at 06:59:36:

On my TEST system, my major source folders are:

SYO System Objects (.ibs, .inc, .obj)
NXT Next generation of .ibs, .inc, .obj

Compiles thru UE work just fine when I'm in SYO
Compiles don't work at all when I'm using sources in NXT

if I start CAPI, compiles of sources in NXT seem to work just fine.

I've checked UE Advanced>Comet Startup (CTRL+SHIFT+5)
and Advanced>Blind Password (CTRL+SHIFT+7)

to make sure the Blind Password is Blanks (nothing filled in)

so it looks like I've got to startup a CAPI session just to do compiles.

since the Blind Password is blank, don't think that's the problem

just can't find a PATH where it points to SYO and not NXT.

would like to free up a session that's now taken up by CAPI however since I usually need all the sessions I have when real testing is done.

Current work around is to generate Compile scrips with maybe around 200 programs in them using MTB. What's slick is that with Comet/32, I don't have to worry about Byte-Alignments.... one less thing to fret about.

Thanx

Bob "A"

P.S. BTW.. have tried compiling both with and without //IB// headers.... didn't detect any difference.


Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?  

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):





Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]