Re: TYP

["Robert Holmgren" holmgren@xxxxxxxx]

** Reply to message from Paul Breeze  on Wed, 15
Dec 2004 15:18:35 GMT


> I have done as you suggest below, and modified U2, then run TYP. However this
> generates no bat file in the editor directory.

> I have also commanded dir c:\progra~1\gs\gs8.50\bin\GSWIN32.EXE but this
> elicits the message 'file not found.' I then tried to explore the directory tree...
> when I tried to examine the directory of c:\progra~1\gs I
> received the 'file not found' message again. The archive attribute
> on "c:\program files" is not set but the read only attribute is set.

It's not the archive bit on C:\Program Files that matters, it's the archive bit
on C:\Program Files\GS -- and *every* directory below it, right down to \bin!
They all have to be cleared. That's what DArchBit.CMD is for: run it against
C: (follow the instructions in the CMD file first, set it to remove archive
bits only).

But regardless, if you don't have a BAT file to execute, what does it matter
where Ghostscript is? First things fist... Because when you say "I received
the
'file not found' message again", sure, it's the same message, but how do you
know which file it is talking about, or whether its the same file? There
*three* potential files that it "can't find":

the BATfile
KMD.EXE
GSWIN32.EXE

Have you double-checked that KMD is indeed in the PATH? Go to a DOS Prompt,
type "KMD" and see if a new instance of command processor opens. (If you
have to type EXIT twice to kill the VDM, then yes KMD was found.)

Maybe its a timing issue. Very fast machine, or very slow machine, very slow
disk writes (or lots of other concurrent processes running maybe?). Use the
attached special (crippled) debug version of TYP (PAULTEST.FRM). CAll a small
one-page text file into current window, and RUN it from the command line:

RUN PAULTEST.FRM

This version will print the file if it can, but it also quits in the middle
(after issuing the command to print the file), and displays the name of the
BATfile on the CMline. You can CAll that file to verify that it exists. Among
other things, this special version loops around if the BAT file doesn't exist.
It will allow you to keep trying to create the BATfile, or to Abort. *Keep
trying*, three or four times. Each time it will wait one second longer than
the previous run before testing to see if the BATfile that it just made
actually exists or not. If it is unable to create the BATfile for some reason,
then something is screwed up at your end.

-----------------------------
Robert Holmgren
holmgren@xxxxxxxx
-----------------------------
Attachment:
PAULTEST.FRM

Description: Binary data