Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 339
  • Last Modified:

Kernel32 not found Error

I recently switched to Windows-98 (no post-conversion warnings, please) and now my compiled Delphi apps won't run on Windows-NT 4.0.  The error message is Kernel32 not found.  Obviously, Kernel32 is there, but it can't find it.  (It is in the Windows\System folder, which is also specified in the search path in the error message.)

Note: The user was using the previous version which used the same DLL and got no error.

Someone has suggested that the problem may be that Delphi (really the VCL) didn't use the explicit DLL extention and NT is not associating the file as a DLL.  How can I fix this ???
0
saintcyr
Asked:
saintcyr
1 Solution
 
viktornetCommented:
Is the Kernel32.dll file in the System directory....???

//Vik
0
 
saintcyrAuthor Commented:
Edited text of question
0
 
d_kiernanCommented:
I noticed a problem like this before, where the app compiled on NT wouldn't work on 95. I don't remember the Kernel32 error though.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
pjdbCommented:
I've had the same problem with NT4. It was because the user have no right the DLL. It can be solved in two way : use the system right in your program or modify the rights of the file.
0
 
saintcyrAuthor Commented:
Edited text of question
0
 
BlackDeathCommented:
well, if the problem actually lies in not-associating that file with the correct extension, why don't you detect the system you're running on (nt/9x) and add it programmatically?

maybe it would be easier to decide what the right solution could be, if you posted some code here...

regs,
Black Death.
0
 
rwilson032697Commented:
Make sure all the API function prototypes that map to kernel32 explicitly name it as 'kernel32.dll' instead of just 'kernel32'

ie: It should be:

external 'kernel32.dll'  (or external kernal32)

rather than

external 'kernel32'

Cheers,

Raymond.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now