This problem is confusing but at the same time should have a simple answer.
We have two different software packages, one is internal software we use to track customers and such. The other is our main product that we sell to those customers.
Here is the problem... The boss got XP for his laptop and wanted the internal software installed to use on the road. However it keep crashing at misc sections of the code. He runs the main product just fine (both coded in dB2K)
All the other workstations in the office runs NT and no one has a problem with either our main product or the internal software.
I ran a little utility on the bosses laptop and found this infomration:
-----
The application read from Users Registry Keys. It should not read this area of the registry directly for user-related information. Registry keys change with each version of Windows. To guarantee compatibility, use the correct API calls.
#DESCRIPTION END
#LOGENTRY RegistryChecks 17 'Wrote to a non-Current User Registry key.
The application wrote to a non-Current User Registry Key. Application should store information to the Current User section of the registry, which allows each user to have their own saved preferences.
#DESCRIPTION END
| RegistryChecks 14 | 2 OLE32.DLL 37962'Read from dangerous registry entry 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager'.
| RegistryChecks 14 | 2 DB2KRUN.EXE 2288AB'Read from dangerous registry entry '|HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\NIs\Codepage'.
| RegistryChecks 14 | 2 DB2KRUN.EXZE 2288AB'Read from dangerous registry entry 'HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\NIs\Codepage'.
The question: What can I do to fix the application from crashing on Windows XP, as this seems like a DB2K problem.
If this post is in the wrong section or can be answered elsewhere, please let me know.
dB2K version: 0.4 b1661
Bosses PC: Fresh install of XP Home
Others: Windows NT4.0
Thank you
Datorz
We have two different software packages, one is internal software we use to track customers and such. The other is our main product that we sell to those customers.
Here is the problem... The boss got XP for his laptop and wanted the internal software installed to use on the road. However it keep crashing at misc sections of the code. He runs the main product just fine (both coded in dB2K)
All the other workstations in the office runs NT and no one has a problem with either our main product or the internal software.
I ran a little utility on the bosses laptop and found this infomration:
-----
The application read from Users Registry Keys. It should not read this area of the registry directly for user-related information. Registry keys change with each version of Windows. To guarantee compatibility, use the correct API calls.
#DESCRIPTION END
#LOGENTRY RegistryChecks 17 'Wrote to a non-Current User Registry key.
The application wrote to a non-Current User Registry Key. Application should store information to the Current User section of the registry, which allows each user to have their own saved preferences.
#DESCRIPTION END
| RegistryChecks 14 | 2 OLE32.DLL 37962'Read from dangerous registry entry 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager'.
| RegistryChecks 14 | 2 DB2KRUN.EXE 2288AB'Read from dangerous registry entry '|HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\NIs\Codepage'.
| RegistryChecks 14 | 2 DB2KRUN.EXZE 2288AB'Read from dangerous registry entry 'HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\NIs\Codepage'.
The question: What can I do to fix the application from crashing on Windows XP, as this seems like a DB2K problem.
If this post is in the wrong section or can be answered elsewhere, please let me know.
dB2K version: 0.4 b1661
Bosses PC: Fresh install of XP Home
Others: Windows NT4.0
Thank you
Datorz