send q lockups bischof_s
from: Greg Goebel / HP-MXD
gvg@lvld.hp.com / 970-679-2305 / FAX 970-679-5971
website: http://hpislsup.lvld.hp.com
to: Stan Bischofs
date: Tuesday, 04 November 1997 1429 MST
>> Otherwise you could try to rename the cfg23232.dll file to something like,
>> c.dll.
>
> Well, that doesn't do it either! (still locks up).
>
> presumably then the other DLL's are for other interfaces and I can
> by process of elimination find out which one locks the system?
The lab guy concurs. The different files all start with "cfg". Please let
us know how this works.
> Stan
>
> ----------------------------------------------------------------------
> Stan Bischof Hewlett Packard Company 707-577-3994 stanb@sr.hp.com
> ----------------------------------------------------------------------
Please stay in touch.
[<>] regards -- gvg
From: Greg Goebel <gvg@hpislsup.lvld.hp.com>
Subject: Re: Re[6]: SICL lockup in NT4?
To: stanb@hpnmrsb2.sr.hp.com (Stan Bischof)
Date: Tue, 4 Nov 97 15:05:36 MST
>
> Hi Greg
>
> Did some fiddling and found that all the DLL's were OK _except_ for
> cfg34132.dll (for the HP HPIB cards). WIth this one in place I/O config
> locks up. Without it all is OK.
>
> Since this is an Omnibook and hence isn't supported by HP (are we ever
> going to support laptops???) it looks like my best workaround is to
Eh? We never claimed that SICL didn't work on a laptop. Now PCMCIA support
is another issue ... we're working on that one.
> comment out this DLL. Not a very comfortable fix but what the heck- it works!
Hmm, have to tag this one in the books ...
> thanks for the hints
> Stan
>
> ----------------------------------------------------------------------
> Stan Bischof Hewlett Packard Company 707-577-3994 stanb@sr.hp.com
> ----------------------------------------------------------------------
>
From: Greg Goebel <gvg@hpislsup.lvld.hp.com>
Subject: Re: Re[8]: SICL lockup in NT4?
To: stanb@hpnmrsb2.sr.hp.com (Stan Bischof)
Date: Tue, 4 Nov 97 15:35:20 MST
> What I meant is that we (HP) offer no I/O solutions for portables, and
> thus I need to rely on 3rd party vendors.
>
> But it sounds like PCMCIA is coming? That would be great. How soon?
I-phase right now ... gvg
From: Greg Goebel <gvg@hpislsup.lvld.hp.com>
Subject: Re: Re[10]: SICL lockup in NT4?
To: stanb@hpnmrsb2.sr.hp.com (Stan Bischof)
Date: Tue, 4 Nov 97 15:39:10 MST
>
> Greg Goebel <gvg@hpislsup.lvld.hp.com> wrote:
> > > What I meant is that we (HP) offer no I/O solutions for portables, and
> > > thus I need to rely on 3rd party vendors.
> > >
> > > But it sounds like PCMCIA is coming? That would be great. How soon?
> >
> > I-phase right now ... gvg
> >
>
> Great- I'd be very glad to be an early tester!
Hang on, we're still trying to get the PCI card out the door.
> Stan
> PS HPIB only or other solutions also?
We seem to be really reluctant to jump into using PC I/O cards for
data-acqusition. So it's HPIB only right now.
[<>] regards -- gvg
from: Greg Goebel / HP-MXD
gvg@lvld.hp.com / 970-679-2305 / FAX 970-679-5971
website: http://hpislsup.lvld.hp.com
to: Stan Bischofs
date: Tuesday, 04 November 1997 1429 MST
>> Otherwise you could try to rename the cfg23232.dll file to something like,
>> c.dll.
>
> Well, that doesn't do it either! (still locks up).
>
> presumably then the other DLL's are for other interfaces and I can
> by process of elimination find out which one locks the system?
The lab guy concurs. The different files all start with "cfg". Please let
us know how this works.
> Stan
>
> ----------------------------------------------------------------------
> Stan Bischof Hewlett Packard Company 707-577-3994 stanb@sr.hp.com
> ----------------------------------------------------------------------
Please stay in touch.
[<>] regards -- gvg
From: Greg Goebel <gvg@hpislsup.lvld.hp.com>
Subject: Re: Re[6]: SICL lockup in NT4?
To: stanb@hpnmrsb2.sr.hp.com (Stan Bischof)
Date: Tue, 4 Nov 97 15:05:36 MST
>
> Hi Greg
>
> Did some fiddling and found that all the DLL's were OK _except_ for
> cfg34132.dll (for the HP HPIB cards). WIth this one in place I/O config
> locks up. Without it all is OK.
>
> Since this is an Omnibook and hence isn't supported by HP (are we ever
> going to support laptops???) it looks like my best workaround is to
Eh? We never claimed that SICL didn't work on a laptop. Now PCMCIA support
is another issue ... we're working on that one.
> comment out this DLL. Not a very comfortable fix but what the heck- it works!
Hmm, have to tag this one in the books ...
> thanks for the hints
> Stan
>
> ----------------------------------------------------------------------
> Stan Bischof Hewlett Packard Company 707-577-3994 stanb@sr.hp.com
> ----------------------------------------------------------------------
>
From: Greg Goebel <gvg@hpislsup.lvld.hp.com>
Subject: Re: Re[8]: SICL lockup in NT4?
To: stanb@hpnmrsb2.sr.hp.com (Stan Bischof)
Date: Tue, 4 Nov 97 15:35:20 MST
> What I meant is that we (HP) offer no I/O solutions for portables, and
> thus I need to rely on 3rd party vendors.
>
> But it sounds like PCMCIA is coming? That would be great. How soon?
I-phase right now ... gvg
From: Greg Goebel <gvg@hpislsup.lvld.hp.com>
Subject: Re: Re[10]: SICL lockup in NT4?
To: stanb@hpnmrsb2.sr.hp.com (Stan Bischof)
Date: Tue, 4 Nov 97 15:39:10 MST
>
> Greg Goebel <gvg@hpislsup.lvld.hp.com> wrote:
> > > What I meant is that we (HP) offer no I/O solutions for portables, and
> > > thus I need to rely on 3rd party vendors.
> > >
> > > But it sounds like PCMCIA is coming? That would be great. How soon?
> >
> > I-phase right now ... gvg
> >
>
> Great- I'd be very glad to be an early tester!
Hang on, we're still trying to get the PCI card out the door.
> Stan
> PS HPIB only or other solutions also?
We seem to be really reluctant to jump into using PC I/O cards for
data-acqusition. So it's HPIB only right now.
[<>] regards -- gvg