Re: Dumbass user or problem with regsvr32
From: Joseph M. Newcomer (newcomer_at_flounder.com)
Date: 03/23/04
- Next message: Joseph M. Newcomer: "Re: DoModal dialog fails with CDateTimeCtrl"
- Previous message: Ajay Kalra: "Re: SplashScreen with a CDialog"
- In reply to: a.m.a: "Re: Dumbass user or problem with regsvr32"
- Next in thread: Kevin D. Quitt: "Re: Dumbass user or problem with regsvr32"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 22 Mar 2004 21:35:43 -0500
I decomissioned my last Win16 machine in 1999; I needed it to check out legacy code, and I
still had a few Win16 products that ran native on Win16 out there. My last client
converted in 1998, and I shut the machine off a few months later.
I kept a Win98 machine alive until a year ago for testing apps; while I could still test
them on my laptop, I'm disinclined to ever develop another app to run on MS-DOS. Nearly
all of my clients are demanding their customers use Win2K or later. I have a Win2K machine
for checkout, and I still maintain an NT 4.0 machine for checkout in the unlikely case
that a client needs validation that the app can run on 4.0. All my client base insists on
Win2K or later; one client has an app that can only run on Server 2003 (because it uses a
Server 2003 enhancement unavailable on earlier machines).
The bottom line is that if you are going to support an app on an operating system, you
need to check it out on that operating system. Nothing else will substitute.
Of course, this may be yet another instance of assuming copy == install, so there could be
all sorts of serious problems with older DLLs that have not been properly updated.
joe
On Mon, 22 Mar 2004 17:02:48 -0500, "a.m.a" <amarcaurele@videotron.ca> wrote:
>
>"Hans Meier" <hmeier@web.de> wrote in message
>news:c3nhlh$b43$00$1@news.t-online.com...
>> Hello,
>> I told a user of my program the use the following command:
>> regsvr32 C:\mdd\mycom.dll
>> He told me that he received an error message box by RegSvr32 saying:
>> "LoadLibrary("C:\mdd\mycom.dll") failed - The specified module could not
>be
>> found."
>>
>> Then I told the user to copy the file. Like this:
>> regsvr32 C:\mdd\mycom.dll -- fails with above error
>> copy C:\mdd\mycom.dll C:\mdd\mycom2.dll -- succeeds
>>
>> So if copy works it's proven that the file exists. So why does RegSvr32
>> fail? The operating system is Win 2000 Server. The cause might be either a
>> strange behaviour of Win2000 server or the insanity of the user. I think
>the
>> latter case is more likely.
>>
>> What do you think? It's an important project we are working on. Thanks.
>
>
>Have you tried to register the library on a win2k server yourself ?
>(as soon as you do, we can stop assuming the user is unskilled)
>
>What OS was used to compile the release version of the library ?
>
>I once had similar errors because i was trying to register a dll on Win98
>that had been compiled on Win2k. Depending on external symbols that
>your application needs to resolve, such a mix of OS can lead to errors.
>I recompiled the dll in Win98, and all subsequent versions of windows
>accepted the registering. On the other hand we dont know what external
>libraries
>your dll needs to run, so who knows. Ultimatly, you should test your DLL in
>Win98/ Me/ 2k/ and Xp. BEFORE shiping a release version.
>
>
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
- Next message: Joseph M. Newcomer: "Re: DoModal dialog fails with CDateTimeCtrl"
- Previous message: Ajay Kalra: "Re: SplashScreen with a CDialog"
- In reply to: a.m.a: "Re: Dumbass user or problem with regsvr32"
- Next in thread: Kevin D. Quitt: "Re: Dumbass user or problem with regsvr32"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
