> 4. How does the installer actually handle installations to locked
> files? Does it do something like a SetupInstallFileEx
> which means that a reboot is really required? I see that the
> script is supposed to warn that the file's not been unloaded,
> but I've never actually seen that warning
> appear even though I've had installation failures.
>
I always thought the DLL version numbers (and file name) were
supposed to be incremented each time a version is released. If this
is happens, will a file-lock problem exist? A new DLL filename with
a new version could be registered and the old in-use one wouldn't
get unloaded until a logout/in. This seems ok to me (with my very
limited understanding), but I dont think it is working as I
described. I certainly agree that the majority of the problems seem
to be related to getting the proper DLL registered and loaded. An
improvement in this area could possibly yield a sizable reduction in
bug reports... IMO of course..
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/
Monty Scroggins
Broadband Data Systems Engineering (BDSE)
MCI Worldcom
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Dqsd-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dqsd-users
http://sourceforge.net/mailarchive/forum.php?forum_id=8601
