Tech Note 01: Common Problems

January 27, 2009

© 2022 NSB Corporation. All rights reserved.

1. Error '429' on starting NS Basic/Palm

Run the file \Program Files\nsbasic\palm\register.bat as Administrator. (In Vista, right click on the file to do so.) This will re register all the controls that NS Basic/Palm uses.

If that doesn't help and you are running Windows 95, your version of the system file ComCtl32.dll may be out of date. Here's a Microsoft Knowledge Base article that tells you how to update it:

2. POSE/Simulator does not work properly

If POSE or the Simulator are clearly running, but NS Basic does not see it (programs do not download or multiple copies of POSE/Simulator are started), then check if your firewall or antivirus software is blocking socket connections. POSE and the Simulator use Port 6415 to send and receive communications. Either set your firewall/antivirus software to allow port 6415, or disable it.

A second possibility is that you are running an old version of Emulink.ocx. If you are running NS Basic/Palm 4, this file should be Version 2. Look for the file in c:\WINNT\System32\Emulink.ocx. (c:\Windows\System32 for older versions of Windows).

We also have a report of Norton Ghost 6.5 causing random hangs when starting NS Basic/Palm.

If you are using the Palm Simulator, check the .ini file in the Simulator folder. Make sure that 68KDebuggerPort=localhost:6415. It is set to different values in some versions of the Simulator.

3. Run Time Error 380 - Invalid Property Value

This is caused by having only True Type fonts enabled. In the Fonts Control panel, in the View Options dialog there's a True Type Fonts tab. In this is a check box entitled "Show only True Type fonts in the programs on my computer". Unchecking this solves the problem.

In some cases, this can be caused by Windows not being able to locate the special fonts that NS Basic/Palm uses. You can fix this by moving the fonts in \program files\nsbasic\fonts into \windows\fonts.

4. 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".

5. Divide error in module GDI.EXE

"I received my copy of NSBasic/Palm this week, and encountered exactly the same problem. I have a K6-2/400, Win95 OSR 2.1, and a Trident AGP 9850 video card. I was running the latest drivers from the Trident web site. In my case, the problem was not the CPU speed or printer driver. It is the video driver. Once I changed my video driver to Windows supplied ones (either Trident Super VGA or Microsoft Super VGA), NSBasic ran fine. Of course, my refresh rates are less than ideal, but at least now I can use NSBasic." -- John Rook

6. "From Object ID #xxxx (...) is completely offscreen."

This message appears in POSE, when you have a Listbox or Popup object that is too near the edge of the screen. When the Palm OS creates the object, it also creates a little scroll arrow along its right hand side. If the normal location of that scroll arrow would be off the screen, this message is produced. The object being referred to is actually (xxxx-1), where xxxx is the object ID number in the message. This error can actually be ignored: when you run your program on a actual device, it will work fine.

7. When trying to install my app, I get "Can't find any username to install programs for...installation cancelled."

You need to do a successful Hotsync first. This initializes the settings within Hotsync so it knows the username.

8. "Unable to find the PalmCntl.ocx" during installation

This can be caused by an old version of Novell Client being installed. Make sure you have at least of Novell Client installed. Another solution (syggested by a Novell employee) is to do the installation in Safe mode.

9. Removing NS Basic/Palm completely

The Windows Uninstaller only removes files that have not been modified since an application has been installed. As a result, uninstalling a package often leaves some files and registry keys. If you do the following, you will remove NS Basic completely from your system. This can be a useful procedure if you want to make a complete clean reinstallation.
  1. Uninstall NS Basic from the Start Menu.
  2. Delete the folder c:\nsbasic. Make sure you back up any files of yours that might be there!
  3. Delete the folder c:\program files\nsbasic.
    If you have NS Basic/CE installed, do not delete c:\program files\nsbasic\CE.
  4. Clean out the registry:
    [Start]...[Run]...regedit. Click on OK.
    Navigate to HKEY_CURRENT_USER\Software\NSBasic.
    Right click on it to delete it.
  5. Delete C:\Windows\Palm OS Emulator.ini if it exists.