#d/l programs
15 messages in this thread
Hello.
I d/l a few programs over the weekend and came up with the following :-
MOVESSP – Virusx 4.0 and 4.01 gave the coldcapture vector not zero msg.
JDIAG – Software error task held and a GURU every time I tried it.
DFC – msg not a dos disk given when running virusx 4.01, and the
disks are inserted after dfc started. No problem using virusx
4.0
Has any one else experienced these problems.
Thanks
Les
I get the 'cold capture vector not zero' on my A3000 under 1.3 but not
under 3.0 when virusx 4.4 loads. I just assumed it was another
incompatibility problem we 3000 users are fast growing to expect.
Dan:
Beware of VirusX 4.4. Steve Tibbett (author of VirusX) just uploaded
the latest version last week, and it is 4.01.
Clint <VRLI>
Clint:
Yes, I was aware that Virusx 4.4 was not a offical version, thanks for your
tip.
VirusX 4.4 is NOT an offical release. Dump it and get version 4.00 or
4.01. Both are in our libraries.
Steve
Steve:
Ok steve, I'll pick up 'official version', hope the author fixes the
A3000 1.3 problem soon thought.
Les,
you WILL get "Not a Dos disk" when you have DFC running in your machine
because it disables the reading of the drives. That is just the way it
works. Once you remove DFC, the disk will be fine if it was before hand.
I was running VirusX when I tried MOVESSP, but I run it with the -r switch
because I have a 2091 drive and need that switch. The program does not
have a virus, but it is possible that it writes to location 0. I don't
know.
JDIAG – I ran that one with no problems at all. Sorry you had trouble with
it. I don't know what the problem might be, since I only unpacked it and
ran it to see that it would run. I must have received three or four
screensful of information about the bridgeboard when I ran it.
……Betty
Hello Betty
Thanks for your reply. Is the non dos disk message an indication of the
way things may work in the future?. I certainly did not get the message
under virusx 4.0. I will ask Steve Tibbett about it
I am also running the R option on both virusx and setpatch.
After you told me that you could run Jdiag, I had a little think about it,
as I have odd Gurus now and then. I found that Jdiag had in fact finished
and was closing down. I checked my shell stack and it was only 4000. I
have now made it 20000, and it cleared my problem with Jdiag. What size
shell stack do you run with
The Jdiag report sample showed that Janus version as 33.4 and 2.66, I am
on version 33.1 and 2.63. The comments at the top of the sample print out
suggested some fixes. Do you know if they are available here on the net
Les
Les, are you running Janus2? I haven't looked closely at the version I am
running, but it came with my AT bridgeboard in February.
The "Not a DOS disk" message,as best I recall, came when you had DFC active
in your computer, but tried to access df0: DFC puts a lock on that disk
and ANYthing you put into the drive will be reported as "Not DOS" until you
remove DFC (which also removes the lock). That is a protection for DFC,
since it expects to be copying disks and does not expect you to change
disks on it!! It is the nature of the program, and is there because of its
purpose.
I'm glad you got the Jdiag working. Are you using VirusX 4.4? Or 4.01?
The 4.4 version was counterfeit – put out by someone other than Steve.
Don't trust it an inch! Get 4.01 from Library 1 if you want the latest.
……Betty
Hello Betty.
Yes I am running Janus2 (sorry that I did not say that), my BIOS is 3.5. I
got the AT last november. What is your version of the bridgeboard.
I am definately not using virusx 4.4, I have versions 4.0 and 4.01 on my
system at present. Generally I run on 4.01 now.
By the way have you heard of any updates/fixes to janus2?. Jdiag suggested
that BIX may have something.
Les
Les, there were some chips that updated older boards, but they came out six
or eight months ago. My board came with the newer chips, and I got it in
January. I do not have an account on BIX, so I don't know what is there.
I have BIOS 3.6, but I forget the Janus numbers. One of them is 33.1, I
forget the other.
……Betty
Les,
I'm using MoveSSP and VirusX 4.01 and I haven't seen the coldcapture
vector not zero message. Did you put MoveSSP as the first command in your
startup-sequence? Also, are you absolutely sure it's MoveSSP?
Brian J. Bartlett
*Shadowjack*
Hello Brian
Movessp was the first line in my startup-sequence, before setpatch R.
I only get the coldcapture message if movessp is started. I have just
enabled movessp and came up with the message. Taking out movessp I get no
message. That is why I am thinking it is from movessp.
Thanks for your interest. I thought I might use the command but if it is
going to give me troubles I will forget it.
I also got the message using virusx 4.0
Les.
Les,
I just tried every configuration I can think of here (moving VirusX
around, just running it, no -N, etc) and I can't duplicate it. Either the
combination of the two loves my hardware/software configuration, or it
hates yours, for some reason.
Brian J. Bartlett
*Shadowjack*