🚀 go-pugleaf

12/21 I talked to RG Software:

According to them the numbers are debugging codes that only beta
versions of 10.0 should display.  The numbers only showed up when
vi-spy was being run by the AUTOVS program, so this could have been
the problem somehow.

Their recommendation: erase the current version of vi-spy and
reinstall from an original disk know to be a release version.

- --dan

[Moderator's note: Thanks for the follow-up, Dan.  This is exactly the
sort of thing that I had in mind with regards to posting product
support questions and summaries here.  I hope that others follow this
example.]

Original post:
> VI-SPY 10.0
> RG Software Systems, Inc.
>
> Has anyone encountered this problem with VI-SPY 10.0?
>
> I have vi-spy running from the autoexec.bat on a Northgate
> 386 that has a Stacker "stacked" drive.
>
> On boot up, vi-spy starts to check for viruses, then it spits
> out four numbers, <<3031>>,<<3120>>,<<E8F4>>,<<4549>>,
> then the system freezes (need to hit the reset button).