Tech Note 01:
The Registry is a file built into the Windows CE operating system. When an application is launched, Windows CE uses the Registry to obtain vital information about how to start an application. Since the Registry is shared by all the applications on a device, if it gets corrupted by one application, others will be affected.
The standard installer that gets built by eMbedded Visual Basic is one of the applications that is known to corrupt the Windows CE registry when uninstalling an app.
The NS Basic/CE Installer needs to put information into the Registry for NS Basic/CE programs run properly. If it is unable to, you will get error messages when you try to run NS Basic/CE.
In most cases, the situation can be corrected by manually entering the commands to register an application. However, if this fails, you will need to recreate your Registry. The only way to do this is to backup your device, give it a hard reset, then reload your applications.
1. (Desktop) Error 429 on startup
This is caused by controls not getting properly registered on installation. This can happen as the result of a corrupted registry. It can be fixed by a batch file that is installed with NS Basic/CE. It needs to be run as Administrator.
This can also be caused by problems in the Registry. This can be corrected by using a registry cleaner utility, such as RegCleaner. Another useful utility is called ActiveXplorer.
2. Make sure you are using the latest version of ActiveSync
This is the software used from the desktop to install NS Basic/CE. If you are running something older than ActiveSync 3.7.1 Build 4034 (The build number is important), you need to upgrade. If you are using something called CE Services, it has been replaced by ActiveSync and you definitely need to upgrade. Get the latest version from Microsoft.
3. Norton Anti Virus: "Malicious script detected" message. Click on "Authorize this script". NAV is being overzealous here. It is objecting to the NS Basic IDE doing a normal operation using a standard Microsoft interface. Authorizing it here will not compromise the security in your system in any way. To permanently stop this message, start Norton Antivirus and go into Options. Under Script Blocking, turn off "Enable Script Blocking".
4. If you get one of the following messages on the device:
5. "Please Reinstall NS Basic" on the desktop or
"PSPC is not a valid integer value" or
Characters in the code window are all "????..."
Some early versions of 4.0 have left an extra file around that needs to be deleted. To fix this error, do the following steps:
6. If you get the following message on your device:
7. (Device) If NS Basic/CE starts, but Visual Designer is not found
This is caused by a bug in Windows CE. You need to load the new version of WCELoad first. From the ReadMe.txt file on the release CD, tap on the link to WCELoad.exe Update.
If your CD was produced before August 31st, 1999, you can also get the WCELoad.exe Update from our website.
9. "Could not find CLSID for VBScript" appears on device
This message appears on Windows Mobile 2003 for Pocket PC devices. These devices do not have certain libraries included in ROM which were on previous units. It means either you have not installed the NS Basic runtime on the device, or your registry is badly corrupted. If it is corrupted, you should do a backup, hard reset and reinstall all software.
If you attempt to install Microsoft ActiveSync, which is not supported in Vista, the subsequent installation of Microsoft Device Center (MDC) will not work properly. You won't get a message. Delete ActiveSync from the system and then reinstall MDC.
regsvr32 %systemroot%\system32\hhctrl.ocx regsvr32 %systemroot%\system32\itss.dllThis problem will affect all .chm files when it happens - not just NS Basic.
If you are still having problems, please contact us at firstname.lastname@example.org. We will be happy to help you!