Argus 3 software and Run-time error '383'

[Ultrapurple]

I have been trying to run the Argus 3 customer control software (V3.0) kindly provided by Bill on his Fire-Tics website.

When I run it I keep getting



I have tried installing the software on different machines, running Windows XP, Windows 7 and Windows 10; all give the same error.

Searching the mighty internet finds many others with the same error, generally associated with Malawarebytes - which I don't have on any of the computers.

Has anyone else succeeded in fixing this problem?

(For clarity, this error is when I run the Argus 3 software, not when I run the installer).

I don't believe it's a problem with the Argus software itself, as that has been in use for many years on other machines (eg at Fire Brigades). Any assistance would be most welcome.

[Bill W]

Nothing specific that I recall.  However a search for 'vb6 error 383' point towards drop down list boxes.  When the software starts the only list box is the COM port select so maybe that is behind it ? Think it can only cope with 1-4

Would have thought a straight WinXP laptop with real serial port as COM1 or COM2 should just work.  There were some fiddles needed at times for port buffers/speed, but I think that was for Win98.

regards
Bill

[Ultrapurple]

Thanks Bill

I don't think I've got a machine with a real COM port - I've used a standard USB-serial adapter - but given that the issue affects other software (eg Malawarebytes) I am pretty sure it's something Microsoft has changed rather than a problem with the Argus software. But I can check if the port installs itself as something outside the range 1-4, that's a good tip.

I think I have one more machine with XP Pro that also has a real serial port. It is air-gapped from all networks because it's a standalone computer that runs a specific device and I don't want any risk of it getting attacked from outside. XP Pro is a bit risky to leave unprotected on t'internet! I use Sneakernet to transfer files in and out as required; the relatively infrequent use and small volume of data concerned make this an entirely viable method of data transfer.

[Fraser]

Interestingly, I have just been buying vintage laptops on eBay for this exact scenario. I bought early Win95 and Win98 era laptops as they tend to come with USB ports in addition to the serial and parallel ports. These laptops use hardware serial and parallel ports that do not cause the issues sometimes found on more modern ‘virtual’ serial ports that are in fact USB Serial bridges.

If you go earlier than the Win95 era of laptop you can lose USB ports, CD drives and sound support. I have some 386 and 496 powered laptops running DOS and Win3.1 but they can be a pain to use as any audio or CD support has to be attached to the Parallel port, PCMCIA port or dedicated expansion connector.

It is a good idea to have at least one well made laptop from the Win95/98 era that offers the usual legacy ports and a CD drive as you can run it in Win95/98 or pure DOS mode for software compatibility purposes. Sadly these vintage laptops have become popular with hard core Retro Game fans and prices can be surprisingly high on eBay. I bought faulty units and repaired them as a more cost effective solution  Be careful buying vintage laptops at low prices that are ‘untested’…. Many may be beyond economic restoration to working condition. Most need a RTC battery as a minimum and the Ni-Mh cells pack I used in Toshiba units are quite expensive. The main battery should be considered ‘end of life’ but is not needed for desktop use… just be wary of Ni-Mh packs leaking electrolyte onto the motherboard !

[Ultrapurple]

Thanks Fraser - sage advice as always.

I do keep machines of various vintages (fairly) readily to hand for just the reasons you mention. My own main PC is Win 7 but the work machine I'm using while (still) working from home is Win 10. I have a couple of stick PCs with Windows 10 but they don't really count as PCs...

Following up on Bill's suggestion I took a look at the COM port allocation for the USB dongle on the XP laptop I've been trying to use. It reported as COM17, so I had a word with Device Manager and reassigned it as COM1. Still had the error 383 though.

I guess my last line of defence / offence is a Windows XP tablet machine that I have skulking around. As far as I know it was updated as far as it could be in terms of Service Packs and it has handled the few USB peripherals I've tried, so let's see if I can persuade the Argus software to run on that. Watch this space...

[SteveT]

Just installed on a Windows 95 VM - and i get the same error of "text" is read only and the software wont load. any ideas?

[Bill W]

The official line (on the original CD) was:

Operating System:
Windows® NT (all versions).
Windows® 2000 service pack 3 or newer.
Windows® XP (all versions).

The Argus®3 software will also normally install and run with Windows® 95, 98 or ME. However some problems may arise with older versions of these operating systems and as Microsoft no longer supports these operating systems, e2v technologies cannot provide full support for them.

I also know that just running the installer on a new Win10 gives the same response so it could well be a default 'error due to something' message rather than the error having any real meaning.

One of the software devs had an odd sense of humour at times .......... used a default of error 42 - 'error due to life, the universe and everything' and never put in ANY useful error messages.

Bill

[Fraser]

42 …. The magic number 

A fellow fan of the Hitchhikers Guide to the Galaxy  Coders can have quite a challenging time with their work, and it can get tedious, so I can understand them placing ‘Easter Eggs’ in their code. However error codes should contain a meaningful comment to the user in determining where the issue resides.

Thank goodness the cameras Infinite Improbability Drive normally behaves itself ! 

[Bill W]

This has now started happening on the old, frozen state, laptop I use for Argus3's.  Not aware of changing anything but now always giving error 383 !

Will advise if I ever find out how to fix it.

So far a clean re-installation with 'replace new files with old' has not worked.

[Bill W]

Stranger still, now tried a second PC, also fully isolated, where the Argus3 software used to work fine and got the same error 383.

[Fraser]

Could it be date related ? A bug in the software that does not like the RTC date read from the PC. Try changing the PC RTC to something a while ago, rebooting from cold and see if the program still throws an error.

Fraser

[Fraser]

I know it is off topic, but seeing this thread has made me so sad…. Ultrapurple (Giles) sits at its top as the OP and I miss that lovely friendly chap May he be at peace.

[Bill W]

That has worked !!   
Ran it back 2 years exactly (2020) and now happy.

The relevant factor may be that the furthest the year goes on the software itself (a drop box to select a year) is 2020.  I'll have to get another camera out and test this some more.  It appears for now that while a camera can show years after 2020, cannot set the year after 2020 by PC or remote control.

Somewhat surprised as when Giles reported this problem my software was still working fine - I checked it.

Bill

[Robert763]

Hi Guys,
Thanks for that. Been having the sme issue.
Changed the year on my old reliable Sony PCG-FX505 (Win XP) to 2017 and all works 

Robert.

[Bill W]

A further update for the record.

Camera happily showing 2024 on the screen, and I could adjust the time on the remote control.  I did not try to change the year, from above that would go wrong.

Status report via the PC software shows 2004.