Steve ..
I'd like to see an extended discussion of the DDVR02 vs. DDVR03 issue
here too. When version 03 first came out I had moved everything around
to version 02. Because almost everything around here is Adaptec and at
the time was either 2940UW or the VLB older version in one box, I hit
the Adaptec bug problem with version 02. The updated version(s) of the
FAM7800 both in the Testcase and the released verions of the Adaptec
code fixed those problems, so in each case where version 02 was in
place, both locally and as well at other sites which I tend, that later
version of the FAM7800 code was installed.
When version 03 came out, I updated, I think, two boxes to version 03
with no problems. I do not know how the issue of the version 03 Adaptec
code and driver operation actually was handled by the version 03, but I
think, in that I don't recall any 'later version should we replace?'
notices, version 03 carried, at least by date, still later versions of
the Adaptec code as well.
So I carried the update out to one remote site which used, at that time,
yet and older Adaptec 2940W controller which has/had an Adaptec BIOS on
it that I've not been able to flash, but has/had never given trouble.
Of all things, this older system also has an ASA slot PS?2 mouse driver
card in that all four serial ports are in use for concurrent running
telecommunications applications all the time. There is no dedicated
mouse system on the board and the plug in mouse enablement card cannot
handle IRQ's of above 9! It happens to be on IRQ5, if I recall this
correctly. That's the only <IRQ9 IRQ left available in that there is no
second paralell port needed at the site.
That site is still on Fix Pack 16 for a number of reasons related to old
hardware, CPU speed, and available older memory capacity.
On installation of the version 03 device driver pack, I hit a mouse
irregularity problem, such as you describe below, I think, but not the
Adaptec problem? The only answer to the mouse problem was to backlevel
the mouse driver to the (or a?) version either from version 02, or
possibly earlier. Without being at the site I can't post the driver
file stamp to research this.
Subsequent to all this, long ago, two weeks ago the 2940W controller
apparently went South and was replaced with a 2940UW IBM version /4
card. I don't know if the BIOS on it can be flashed, but Will Honea
posted in response to my question about it, that it likely could be
flashed. It is working fine at version 03 Adaptec driver code levels
with HPFS on the later UHPFS SYSINSTX which had to be done long ago to
stop the earlier Adaptec corruption of HPFS partitions I worked doggedly
to fix when all this 2940UW corruption first appeared back about Fix
Pack 12 or so.
So I've left the version 03 code alone there, and avoided carrying
version 03 updates to any of the other sites I tend, except via complete
upgrades to them via MCP1/MCP2 migrations.
I need to know if you migrate to MCP1 and/or MCP2, that essentially you
will get DDVR03 level code. It is *NOT* necessary to try to apply
DDVR003 to MCP1/MCP2, right? Am I not right that when I tried this, the
SERVICE 1.44 level toolset told me something like, 'Already at current
level, no update necessary.", when attempted against an MCP1/MCP2 box?
So .. in review, what levels of all this are automagically installed by
MCP1/MCP2? And don't count, in certain circumstances, on your mouse
working correctly with version 03 of the drivers, per me findings. You
may have to backlevel to get it working for some cases.
device Driver fixpack 2 is actually better than device driver fixpack
3 IMO.
Why is that? If I remember correctly, DD02 had buggy mouse and
Adaptec 2940 drivers (and maybe one other that I am forgetting). Of
course, you can update those separately... but what do you dislike in
DD03?
--
--> Sleep well; OS2's still awake! ;)
Mike Luther