Probably the GDIPlus.DLL file. It was a new dependency with VFP 8.
I doubt reinstalling the OS will be the trick <g>.
Rick Schummer
White Light Computing, Inc.
-----Original Message-----
From: profoxtech-bounces At leafe .DO.T com [mailto:profoxtech-bounces@leafe.com] On
Behalf Of Whil Hentzen (Pro*)
Sent: Monday, October 31, 2005 10:43 PM
To: profoxtech At leafe .DO.T com
Subject: Registering a VFP DLL (round 2)
Hi folks,
OK, I'm back at it again....
Got a VFP DLL that I compiled (multi-user) in 8.
Runs fine on my dev machine.
Got a NT 4 server that I need to use it on.
This box doesn't have VFP at all on it.
As administrator of the box, I popped the DLL into c:\winnt\system32 (along
with the VBR and TLB) and the two VFP runtimes (vfrp8r.dll and
vfp8renu.dll). Ran regsvr32 on the fully qualified path name.
Got an error about DllRegisterServer failed (0x80004005). Googling on the
error provides (1) all sorts of whining, (2) a few suggestions about using
the VB packager (!?!), (3) wags about reinstalling the entire OS, and (4)
not much else.
Ideas?
Whil
[excessive quoting removed by server]
©2005 Rick Schummer |
