Re: CLIP Woes

["Robert Holmgren" holmgren@xxxxxxxx]

** Reply to message from Michael Norman  on Tue, 28 Dec
2004 21:10:12 -0500


> instructions say to put
> KMD.EXE in the *first* directory in the path. For me that's actually a kind
> of distant subdirectory: C:\PROGRAM
> FILES\THINKPAD\UTILITIES;C:\WINDOWS\SYSTEM32;C:\WINDOWS......

Put it in C:\WINDOWS\system32. Move the THINKPAD dirs further back in the PATH
spec. IBM has a habit of adding their PATHs to the front of the spec -- better
to be first than last. But system32 *should* be first.

> [Harry:] BTW, you could always just put kmd.exe in your
> root, then preface the above path with C:\;

Not a good idea. There's nothing in C:\ that needs to be used by the operating
system. It's a waste of time & squandering of potential speed. All this stuff
should go in system32.

> 3. What am I missing. I must be reading something wrong. The .FRM files are
> inserts for editions of U2 older than 117, right? Wrong?

Right. Use the versions of the FRM files that are in v117.

> It never hurts to ask a stupid question: you do allow it enough time to
> work, right? Because it can take a few seconds on my system, and more for
> longer pasting.

It's only stupid insofar as there's no way for you the user to "allow it enough
time to work". It takes care of that detail internally (frame AWAITFILE).

Problem may be here: Command:
 REGEDIT EXE_or_VBS
What does this REG spec say? Should be "E", in your case, i.e. the stanza
should read:

[EXE-VBS]
;"E" or "V"
EXE_or_VBS=E
;

If missing, add it.

-----------------------------
Robert Holmgren
holmgren@xxxxxxxx
-----------------------------