----------
From: Jerry Chirico[SMTP:jchirico@symca.com]
Sent: Wednesday, March 04, 1998 4:45 PM
To: Smackin
Subject: HPIB problems
Mike,
Your problem was forwarded to me by a co-worker who monitors the VEE
reflector.
What HPIB card are you using? The reason I ask is this:
On our NT systems, you cannot see our Hewlett-Packard HPIB card in Windows
NT Diagnostics !!
You may be misinterpreting another card as the HPIB card. So we first look
at the available IRQs and then set the board to one that is available.
Even after everything is working, you still cannot see the HPIB card in
Windows NT Diagnostics. Only the IO Config program sees it.
Another possibility is plug and play (PCI) bios (even though NT doesn't
support plug and play). If you have plug and play bios, it may only have
one available IRQ left for PCI cards. If the HPIB card and ethernet cards
are PCI they may be forced on each other by the PCI bios.
My suggestion is to pull the ethernet card completely. Go through the HPIB
installation and see if it works properly.
Sorry I can't pin point exactly, but we have seen problems like this before
and they were solved by careful management of IRQs. In one case, just
recently, we were forced to remove a PCI Ethernet card which received it's
IRQ from the BIOS and replace it with an ISA card which had a setup
utility. That solved the problem of 2 PCI cards trying to grab the same IRQ.
**********************************************************
Jerry Chirico
Senior Project Engineer
Symtx, Inc.
19200 Stevens Creek Blvd. #120
Cupertino, CA 95014
mailto:jchirico@symca.com Tel: (408) 343-3610 x25
mailto:jchirico@symtx.com Fax: (408) 343-3616
Here is an excerpt from a bug-resolution that I had just recieved. I
feel the work around is unsatisfactory. What are your opinions? I
submit bugs and enhancement requests often, so should you all.
This is a bad work-around. There shouldn't have to be a work-around.
The fix should be in the control, not in the code I have to write.
The control does not work, in my opinion, as it is supposed to. The
drop-down and pop-up lists should ALWAYS have a timeout feature.
Ciao,
Andrew
______________________________ Reply Separator _________________________________
Subject: vee defect VXDaa17570 was moved to state R by dougk
Author: ddts-at-lvld (ddts@hplvl212.lvld.hp.com) at HP-PaloAlto,shargw6
Date: 3/4/98 10:11 AM
Bug VXDaa17570 vee Submitted 971030
RESOLVED defect Assigned 971106
4.0 Opened 980304
Resolved 980304
"Drop-Down List is modal, could it have a timeout?"
Detection method: in-house normal use
Platform: all
Severity: 5
Frequency: 3
Consequences: 2
Workaround: 0 RESOLUTION INFORMATION
Resolution: no fix
Module[s]:
Fix time (hrs): 0
SUBMITTER INFORMATION
Submitter: andrew hamilton
Organization: HP MXD
Address: andrew_hamilton@hp.com
************ Problem (Added 971030 by http) ***********
The drop-down list of a drop-down-list-box behaves modally, but it has no
time-out feature. Could the drop-down list box have a timeout feature?
ie...It is possible for a user to activate the drop-down list box, but not make
a
selection, therefore hanging up my program. The only other selection control
that has this limitation is the pop-up listbox.
Perhaps the philosophy could be that no selection controls will be modal: unless
they have a timeout feature.
Of course, then the user has to process the timeout.
************ Workaround (Added 980304 by -----) ***********
You can effectively get this behavior by building it into your program.
Take a look at Solitaire.vee and the Options dialog box. You simply
need to keep track of values and then add 'Exit UserObject' objects to
the context.