The installation program for the “Pronto PRO Serial Debug System” used with the Pronto TSU9600 Base Mod (developed by Barry Gordon) does not execute with Windows 11.
Normally it is an extremely easy and quick install. I just double-click the setup.exe file (as administrator) and a screen pops up that says “Welcome to the ProntoPRO Debugger installation program”. On Windows 11, the screen never pops up and basically nothing happens. Does anyone have any potential work-arounds? I happen to use the program quite often.

There are 4 files in the original setup zip.

A .CAB file, a .doc file, setup.exe, and setup.LST

Do you have all 4?

If you have Winrar, you can open the .cab file to see the various COM (Component Object Model) components that must be registered by calling RegSvr32. The SETUP.LST file has the details of what actions the setup program is supposed to take. If not working you can try registering things manually.

I don't have Win11 and only Win7 32-bit but I know this worked then as I updated my machine to use it.

Thanks Lyndel. I do have the 4 files in the original setup zip. Ran them on a Win10 work PC today and it executed perfectly. Ran again on my new Win11 machine and essentially nothing happened.

I did open the SETUP.LST file. While this is likely a very easy install for someone more technically proficient, it is well beyond my understanding. Is it possible this just distills down to moving a few files to C:\Program Files (x86)\ProntoPRO Debugger and several others to C:\windows\system32. Then registering various components?

If anyone can provide just a little guidance, I'll try to figure it out and repost.

SETUP.LST File below:

[Bootstrap]
SetupTitle=Install
SetupText=Copying Files, please stand by.
CabFile=Pronto PRO Debugger.CAB
Spawn=Setup1.exe
Uninstal=st6unst.exe
TmpDir=msftqws.pdw
Cabs=1

[Bootstrap Files]
[email protected],$(WinSysPathSysFile),,,6/1/99 12:00:00 AM,101888,6.0.84.50
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,5/31/98 1:00:00 AM,22288,4.71.1460.1
[email protected],$(WinSysPathSysFile),$(TLBRegister),,7/13/09 7:43:53 PM,16896,6.1.7600.16385
[email protected],$(WinSysPathSysFile),,,11/20/10 8:18:04 AM,67584,6.1.7601.17514
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,11/20/10 8:20:49 AM,90112,6.1.7601.17514
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,8/27/11 12:26:27 AM,571904,6.1.7601.17676
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,7/13/09 9:15:50 PM,1386496,6.0.98.15

[IconGroups]
Group0=ProntoPRO Debugger
PrivateGroup0=True
Parent0=$(Programs)

[ProntoPRO Debugger]
Icon1=""Pronto PRO Debugger.exe""
Title1=ProntoPRO Debugger
StartIn1=$(AppPath)

[Setup]
Title=ProntoPRO Debugger
DefaultDir=$(ProgramFiles)\ProntoPRO Debugger
AppExe=Pronto PRO Debugger.exe
AppToUninstall=Pronto PRO Debugger.exe

[Setup1 Files]
File1=@Pronto_PRO_Debugging.doc,$(AppPath),,,7/20/07 3:43:03 PM,29184,0.0.0.0
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/24/98 12:00:00 AM,103744,6.0.81.69
File3=@Pronto PRO Debugger.exe,$(AppPath),,,8/20/12 8:30:20 PM,135168,1.0.0.0

Before doing full install of DLLs, worst case, try to run the .exe standalone first and see if it will load. Could be that Win 11 already has these dlls.

For the items that are dll self register and don't already exist on your system...

Open a command prompt in Admin mode.

cd /d C:\windows\system32
regsvr32 dllname

for the .tlb, I presume it's already in Windows 11

The ones you are most interested in are

MSCOMM32.OCX
msvbvm60.dll
comcat.dll

vb6stkit.dll is the VB6 setup dll and don't think you will need it.

I tried to run Pronto PRO Debugger.exe first. The message “Component ‘MSCOMM32.OCX’ or one of its dependencies not correctly registered a file is missing or invalid’. Based on your reply, I was going to do the following:
1 - Move MSCOMM32.OCX, msvbvm60.dll, and comcat.dll into the C::\windows\system32 directory
2 - Open a command prompt in Admin mode
3 - cd /d C:\windows\system32
4 - regsvr32 msvbvm60.dll
5 - regsvr32 comcat.dll

Given MSCOMM32.OCX is not a dll file, is there anything else I need to do with it?

Lyndel – As you can probably tell, I have no clue what I’m actually doing. But getting this program working is important – I do use it all the time.

Please ignore my last message. I did get the program to run using the following steps:

1 - Moved MSCOMM32.OCX to C:\Windows\SysWOW64
2 - Opened up a command prompt in Admin mode
3 - cd C:\Windows\SysWOW64
4 - regsvr32 MSCOMM32.OCX
5 - regsvr32 msvbvm60.dll
6 - regsvr32 comcat.dll

Then I just ran the "Pronto PRO Debugger.exe" and it opened!

Now I have to test it with my Pronto TSU9600 and see if it is working properly.

Thanks for your help Lyndel!

.OCX (Ole Control Extension) is a Visual basic Control and the file is a DLL.

So yep, if you see the window for the Debugger, I'm 99% sure you got it right!

Now I did notice you used 2 different folders. c:\windows\system32 and c:\windows\SysWOW64

Assuming you want to put all the .dll and .ocx into same folder (SysWOW64), you'll need to unregister from old location and then re-register in new location.

From command prompt do:
cd c:\windows\system32
regsvr32 /u

Move/copy the files from c:\windows\system32 to c:\windows\SysWOW64

then from command prompt do:
cd c:\windows\SysWOW64
regsvr32

if you run regsvr32 with no parameters, it should give you a popup explaining what each of the options do.

Lyndel

Last edited by Lyndel McGee on January 22, 2022 15:44.

In Windows 11, both the msvbvm60.dll and comcat.dll were already in the Windows\SysWOW64 folder. MSCOMM32.OCX was not on the C: drive at all.

I added the MSCOMM32.OCX file (from Barry's .CAB) to Windows\SysWOW64. Then I registered all three - MSCOMM32.OCX, msvbvm60.dll, and comcat.dll. The program is now working perfectly!

Thanks again.