home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Windoware
/
WINDOWARE_1_6.iso
/
drivers
/
wincobra
/
readme.txt
< prev
next >
Wrap
Text File
|
1991-05-28
|
38KB
|
1,339 lines
Vermont Microsystems
Windows 3.0 Driver for Cobra Elite and Cobra Plus
Installation Notes
VERSION 1.00
TABLE OF CONTENTS
1... INSTALLATION PROCEDURE
2... KNOWN PROBLEMS
3... NOTES
4... IF YOU HAVE PROBLEMS...
5... TECH NOTES
6... BUGS FIXED FROM VERSION 0.95 (beta)
7... KNOWN BUGS
INSTALLATION PROCEDURE
1. If you have not already done so, install the Cobra Elite or
Cobra Plus graphics processor in you system as per the installation
Guide. Be sure to run INSTALLV to ensure that the DOS driver and
firmware is properly loaded.
2. If you have previously installed an earlier version of the
Windows driver, SETUP will not copy the new driver files over
This is a bug in the Microsoft SETUP. To insure proper operation
delete the file COBRA.DRV from the \WINDOWS\SYSTEM directory.
3. Run Windows SETUP either from the Windows 3.0 distribution
diskettes or the WINDOWS directory if you have previously
installed WINDOWS 3.0. Do not run SETUP from Windows. The option
to install a third party ('Other') driver will not appear.
4. Under the 'SYSTEM INFORMATION' Menu, select the DISPLAY option.
5. In response to the 'SELECT DISPLAY from the following list' prompt,
select 'Other'. This should ask you for the diskette supplied by
Vermont Microsystems containing the Windows 3.0 driver.
6. The Windows 3.0 driver files are contained in a subdirectory on
the disk called \WIN3. When prompted as to where to find the disk
and requested files, make the response box look like
(assuming diskette in A: drive):
A:\WIN3
7. In response to the 'SELECT DISPLAY from the following list' prompt
select:
Vermont Microsystems Cobra Elite and Cobra Plus
8. Follow the rest of the Windows SETUP procedure normally.
12. The Cobra Elite or Cobra Plus driver is now fully installed
in the Windows 3.0 environment.
KNOWN PROBLEMS
1. Older, incompatible version of the Novell Network have cause
intermitant hangs. If the Windows Setup procedure did not like
your network configuration and you are running in a network
environment you may run into problems.
2. Older versions of QEMM.SYS in your CONFIG.SYS at setup time can
cause problems while running SETUP. Save your current CONFIG.SYS,
delete the QEMM.SYS line from you CONFIG.SYS and rerun SETUP.
NOTES
The Windows 3.0 default color scheme results in a dithered
Active Window Title Bar for 4-bit boards. This results in a
small performance degradation. The color scheme can be modified
via the Control Panel.
IF YOU HAVE PROBLEMS...
Common errors for Windows installation are:
1. CONFIG.SYS line not modified as per step 2 in the Installation
Procedure above.
2. Older versions of QEMM.SYS in your CONFIG.SYS at setup time can
cause problems while running SETUP. Save your current CONFIG.SYS,
delete the QEMM.SYS line from you CONFIG.SYS and rerun SETUP.
3. Most Windows problems are Windows environment problems. We
strongly recommend using the Microsoft supplied MOUSE.SYS,
HIMEM.SYS and SMARTDRV.SYS. These drivers control the mouse,
manage extended memory and cache disk requests respectively.
Using other drivers to perform the same functions can cause
problems.
4. Many Windows 2.0 applications will run under Windows 3.0. In
the Windows 3.0 environment they generate an error message but
the option exists to ignore the error message. While the
application may appear to run correctly corruption of the
environment may be taking place. Take these error messages
seriously. Update the application or use sparingly.
5. Before calling technical support with a problem, look
through the TECH NOTES section and the KNOWN BUGS section.
Your problem may be addressed there.
WINDOWS TECH NOTES
Tech Note
Windows 3.0 Native Driver
Title: Divide error when trying to start Windows
Date: 26-Mar-91
By: evh
When invoking Windows it may fail to switch into high res mode and simply
return to DOS, giving a divide error. The reason Windows fails is
for one of two reasons:
1) The driver was unable to open the DOS driver
2) The driver was unable to create the on-board buffer
the Windows driver uses.
The reason the divide error is reported is apparently a bug in
Windows. The function which opens the driver is supposed to return
a structure length upon success and zero upon failure. It looks like even
when zero is returned Windows tries to perform some arithmetic
operation using the 'structure length'.
Tech Note
Windows 3.0
Title: Setup hangs when run from DOS
Date: 18-April-91
By: evh
The Microsoft Windows Setup program can be run in one of three ways.
First, it can be run from inside of Windows. When invoked this way
the 'other' option for display drivers is not available, so our
driver cannot be installed in this way.
Setup can also be run directly from the Windows distribution disks.
The only disadvantage to this is that if Windows has already been
installed, it must be completely reinstalled. This is very
time consuming.
The preferred way of installing the VMI driver when Windows has
already been installed is to invoked Setup from DOS. Unfortunately,
there is a known bug in Setup which causes it to hang occasionally
when invoked in this manner. If this happens, the only option is to
install Windows from the distribution disks.
Tech Note
Windows 3.0
Title: Different installations for 5 1/4" and 3 1/2" format disks
Date: 18-April-91
By: evh
The Windows Setup program uses a script file called setup.inf.
Likewise the VMI driver disks contain a companion script file called
oemsetup.inf. These files contain commands for the Windows
installation, including such things as what disks contain which
files. Because there are a different number of disks for Windows
depending on whether it came on 5 1/4" floppies or 3 1/2" floppies,
the setup.inf files are different. Therefore, you must be very
careful about mixing and matching Windows and VMI format floppies.
The indication of this problem will be that Windows will ask the user
to insert a particular disk, then give a "file not found" error.
Because of this problem, VMI ships the oemsetup.inf files for both
formats. They will be named oemsetup.514 for the 5 1/4" floppy
format, and oemsetup.350 for the 3 1/2" floppy format. There will
also be a file names oemsetup.inf. This will be the file for the
floppy format on which the driver resides. If you need switch to the
other format, simply copy the appropriate oemsetup file over the one
named oemsetup.inf.
Tech Note
Windows 3.0
Title: Switching between CV and Microsoft Windows
Date: 18-April-91
By: evh
This tech note was copied from a technical bulletin written by:
4D Graphics ESS
1800 NE 44th Street
Suite 210
Renton, WA 98056
It is included here as a service to VMI customers. The validity of
the information cannot be verified by VMI. If you have any questions
please contact 4D Graphics ESS.
*************************************************************
Microsoft has created their own 386 specification, "DOS Protected
Memory Interface" (DPMI), which is not compatible with "Virtual
Control Program Interface" (VCPI), required by Personal Designer.
DPMI is part of the HIMEM.SYS device driver installed by the Windows
installation program. If HIMEM.SYS is installed on your system,
Personal Designer will not run. Instead it produces a somewhat
cryptic error message such as "Cannot lock stack page frame." Until
recently the best way to get around the problem has been to maintain
two different CONFIG.SYS files, and re-boot your system with each
configuration.
Recently QuarterDeck (213-392-9701) has released a new version of
their QEMM memory manager (version 5.11) which can provide VCPI
memory for the Personal Designer and other programs, and DPMI memory
for Windows at the same time.
Qualitas Software (301-907-6700) has also released version 5.10 of
their 386MAX and BLUEMAX (for PS/2's) memory managers with similar
capabilites.
Even with these utilities Personal Designer cannot run while Windows
is running in 386 Enhanced Mode. However, running either of the
products named above instead of HIMEM.SYS, GCD can at least be run
from inside of Windows real mode, Windows standard mode, or from DOS.
Due to potential conflicts between device drivers, it is best to run
Personal Designer from inside of Windows using either dual screens
(say a VGA for Windows and a high performance card for Personal
Designer), or sharing a simple device such as VGA or EGA.
*************************************************************
Tech Note
Windows 3.0
Title: Fonts that do display properly with the VMI Cobra Driver
Date: 19-April-91
By: evh
This problem showed up when we switched from a VGA driver to the
Cobra driver. The ZapfDingbats font characters did not display.
Everything printed properly, but the characters were displayed in
Courier.
Windows has two types of fonts (stored in files with the extent
'.FON'). Some fonts are scaleable and can be used with displays of
any resolution. In the win.ini file they are specified by 'All res',
as in:
Modern (All res)=MODERN.FON
Other fonts are resolution specific. They are specified by the
device that most closely matches the font, as in:
Helv 8,10,12,14,18,24 (8514/a res)=HELVF.FON
or:
Courier 10,12,15 (VGA res)=COURE.FON
Some fonts are provided with Windows, but others must be obtained
elsewhere. If the font is, for example, a Postscript font that
displays on a VGA but not the Cobra Elite or Cobra Plus, the problem
is that the screen font which corresponds to the Postscript font must
be loaded. VMI's Cobra boards are set up to use fonts at the 8514/a
resolution.
One source for screen fonts is Pacific Page which makes the
Postscript add-on cartridges for HP laser printers.
Tech Note
Windows 3.0
Title: DOS box won't work in 386 enhanced mode
Date: 24-April-91
By: evh
On older machines the default vga Virtual Device Driver (VDD) and 386
grabber don't always work. The symptom is that when attempting to
run the DOS box - in either full screen or windowed mode - Windows
reports that the version of 386 Windows is out of synch and that 386
Windows should be reinstalled.
The way our driver is installed, we use the default Windows vga
grabbers and VDD. The default Windows VDD is actually in the Windows
kernel. You can tell this because in the system.ini file the name of
the VDD is *vddvga. The '*' means that 'vddvga' is in the kernel.
All the other VDD's are separate files with a file extent of '.386.'
Starting in version 1.00 of the Cobra Elite driver, and in all
versions of the Cobra Plus driver, the 386 grabber and the VDD are
included. However, in version 0.95 of the Cobra Elite driver this
problem may show up.
Tech Note
Windows 3.0
Title: Using The Bitstream Facelift
Date: 1-May-91
By: evh
The current version of the Bitsream Facelift (Bitstram fonts) will
not work with the Cobra Elite/Plus Windows 3.0 driver. Here is what
we know about why it doesn't work:
When the Windows driver is invoked, the following happens:
1) A function called Inquire gets called. It doesn't really do
anything.
2) A function called Enable gets called twice. The first time it is
called, the driver is supposed to return information about itself in
a structure called the GDIINFO structure. The caller passes a pointer
to a data area into which the GDIINFO structure is to be copied.
Enable returns in the AX register the size of the GDIINFO structure.
If there is an error, Enable returns 0.
3) The second time Enable gets called, the hardware gets physically
enabled. This is where we - normally - switch into high resolution
mode.
What is happening with the Bitstream Facelift is that the first time
Enable gets called, we do exactly what we are supposed to and
everything looks great from our standpoint. The DOS driver is opened
successfully, we create our off-screen memory buffer, we copy the
GDIINFO structure and return its size - which happens to be 6E hex -
in the AX register. Great. Wonderful.
Unfortunately, however, the Bitstream shell apparently doesn't like
what we are returning in the GDIINFO structure because it continues
to call Enable asking not to physically enable the hardware, but to
return the GDIINFO structure. When running without a debugger, this
puts you into an endless loop. When running with a debugger, it
eventually gives up and lets you quit.
As far as I can tell, we are doing everything perfectly legally and
according to the spec, so I don't know of anything I can do to make
this work. We have contacted Bitstream and are awaiting a reply.
Tech Note
Windows 3.0
Title: Non-Windows applications that won't work in the DOS box
Date: 6-May-91
By: evh
Not all non-Windows applications will work in the DOS box. In
Windows terms, they must be 'well-behaved.' Microsoft provides
developers with a list of the things that must be done to make their
non-Windows applications well-behaved.
For example, applications cannot write directly to screen memory.
They must use interrupt 10 to write to the screen. Microsoft
provides a way for applications to detect if the are running under
Windows so they can modify the way they deal with screen memory.
Non-Windows applications must also properly save and restore
interrupt vectors. In general, changing interrupt vectors will get
you into a lot of trouble when running under Windows.
The utility program XTNET is a known application that is not
well-behaved. There are sure to be others.
Tech Note
Windows 3.0
Title: Problems with Windows Setup and Virtual Display Driver
Date: 20-May-91
By: evh
Starting with version 1.00 of the Cobra Elite/Cobra Plus driver, VMI
is shipping its own Virtual Device Driver (VDD) and 386 grabber.
This solves a problem some people were having running the DOS box,
especially on older machines. Unfortunately this also uncoveres a
bug in the Windows Setup program. This bug only occurs when doing a
full install from the Windows distribution disks. It does not happen
when running Setup in maintenance mode.
When installing a third-party VDD, Setup correctly copies the VDD
from the oem disk. Unfortunately, it also prompts for the VDD later
in the install cycle when Windows is installing files from disk #4
(on the 5 1/4" disks) which is where Microsoft's VDD's are. Usually
Setup displays a dialog box with the message:
Please insert the following disk:
followed by the name of the disk. This is followed by an edit box
with the name of the disk driver and sub-directory where the file can
be found, i.e.:
a:
When there is a third-party VDD, the name of the disk and the edit
box are both blank. If you happen to know enough to put the oem disk
back in the driver and enter the correct driver letter and
sub-directory, Setup will continue and run fine. Users should put
the VMI disk in the driver and enter:
a:\win3
in the edit box (when installing from driver a:).
Microsoft is aware of the problem. There is a tech note on their
bulletin board. It is not clear whether they plan to fix it.
Tech Note
Windows 3.0
Title: Windows Setup puts ega.sys in config.sys
Date: 24-May-91
By: evh
There is a but in the Microsoft Windows Setup program which puts the
following line in your config.sys file:
device=ega.sys
This line should be deleted. the ega.sys file is not copied onto
your disk unless you install the ega display driver.
BUGS FIXED FROM VERSION 0.95
Software Change Order
Windows 3.0 Driver
Date: 4/10/91
Reported By: Dotti via email to Eric and Michelle
Found in Version: 0.91
Priority (1,2 or 3): 1
Problem:
Open PageMaker 4.0 publication. Multitask to Program Manager and open
Arts and Letters. Draw filled triangle and rotate the triangle 20
degrees. Reduce the size dynamically to a small size. Cut or copy the
art to the windows clipboard. Try to multitask back to pagemaker.
cursor freezes, need to reboot.
Fixed By: evh
Date: 29-April-91
Fixed after version: 0.95
Fix:
This problem actually occurred any time you switched to PageMaker.
The segment register for the enabled_flag was being clobbered, so the
right offset in the wrong segment was being set. Now the ds register
gets reloaded when the enabled flag is restored. All better now.
Modules affected:
trn_pal.asm
Software Change Order
Windows 3.0 Driver
Date: 3-Apr-91
Reported By: evh
Found in Version: 0.91
Priority (1,2 or 3): 2
Problem:
Most of the cursors that are created when tools are selected in Paint
do not show up (try the paint can).
Fixed By: evh
Date: 30-April-91
Fixed after version: 0.95
Fix:
Paint draws these missing cursors by calling Output and drawing
polylines into a memory bitmap. The code to draw into memory bitmaps
had been inadvertently commented out, so the cursor was never being
drawn.
Modules affected:
Polyline.asm
Software Change Order
Windows 3.0 Driver
Date: 4/10/91
Reported By: jlk
Found in Version: 0.91
Priority (1,2 or 3): 3
Problem:
Windows 3.0 can't be started after enabling Bitstream FaceLift.
Activation of FaceLift modifies SYSTEM.INI "display.drv=cobra.drv" to
"display.drv=shellscr.drv". Product works fine in VGA mode.
Fixed By: evh
Date: 1-May-91
Fixed after version: NF
Fix:
The current version of the Bitsream Facelift (Bitstram fonts) will
not work with the Cobra Elite/Plus Windows 3.0 driver. Here is what
we know about why it doesn't work:
When the Windows driver is invoked, the following happens:
1) A function called Inquire gets called. It doesn't really do
anything.
2) A function called Enable gets called twice. The first time it is
called, the driver is supposed to return information about itself in
a structure called the GDIINFO structure. The caller passes a pointer
to a data area into which the GDIINFO structure is to be copied.
Enable returns in the AX register the size of the GDIINFO structure.
If there is an error, Enable returns 0.
3) The second time Enable gets called, the hardware gets physically
enabled. This is where we - normally - switch into high resolution
mode.
What is happening with the Bitstream Facelift is that the first time
Enable gets called, we do exactly what we are supposed to and
everything looks great from our standpoint. The DOS driver is opened
successfully, we create our off-screen memory buffer, we copy the
GDIINFO structure and return its size - which happens to be 6E hex -
in the AX register. Great. Wonderful.
Unfortunately, however, the Bitstream shell apparently doesn't like
what we are returning in the GDIINFO structure because it continues
to call Enable asking not to physically enable the hardware, but to
return the GDIINFO structure. When running without a debugger, this
puts you into an endless loop. When running with a debugger, it
eventually gives up and lets you quit.
As far as I can tell, we are doing everything perfectly legally and
according to the spec, so I don't know of anything I can do to make
this work. We will have to work with Bitstream, to see if we can
locate the source of the problem.
Modules affected:
None.
Software Change Order
Windows 3.0 Driver
Date: 18-April-91
Reported By: evh
Found in Version: 0.92
Priority (1,2 or 3): 3
Problem:
In dev_to_foreground we blindly load all 256 palette entries. We
need to pull the logic out of vga.asm (physical_enable) to properly
reload the system colors when returning from the DOS box. Otherwise
apps like CorelDraw won't work when returning from the DOS box.
Fixed By: evh
Date: 1-May-91
Fixed after version: 0.95
Fix:
This turned out to be a non-problem. This is how the base code
works. Apparently apps that load their own palettes call
UpdateColors when you switch to them, so blindly reloading all 256
colors in the palette is ok.
Modules affected:
None.
Software Change Order
Windows 3.0 Driver
Date: 18-April-91
Reported By: RS
Found in Version: 0.91
Priority (1,2 or 3): 3
Problem:
In PageMaker 4.0, select a block of text and drag it around. The
block alternates between white on black and black on white. It looks
like another one of those Rop problems where the Rop is being
accumulated directly on the board instead of NDM.
Fixed By: evh
Date: 1-May-91
Fixed after version: NF
Fix:
This is a performance problem. I tried applying the Rop directly to
the screen, using NDM and using Cblt. They are all slow as death.
When we do the performance tune this will be a good test, but it will
have to wait.
Modules affected:
None.
Software Change Order
Windows 3.0 Driver
Date:April 18
Reported By: Dotti
Found in Version:Latest (loaded today)
Priority (1,2 or 3): 3
Problem:
Moving art elements around in PageMaker 4.0 leaves "tracks" on the
screen. Also noticed this phenomenon in the early stages of the
X/Series driver. (386, I think)
Fixed By: evh
Date: 1-May-91
Fixed after version: 0.95
Fix:
This one went away.
Modules affected:
None.
Software Change Order
Windows 3.0 Driver
Date: 24-April-91
Reported By: evh
Found in Version: 0.92
Priority (1,2 or 3): 3
Problem:
I can't always make my driver run with the default vga grabber and
vdd. The default vga vdd is actually located in the kernel, and it
seems to work with most machines. However, with my machine I can't
run the DOS box unless I build the vda vdd and grabber that come with
the DDK. At some point we ought to insert the DDK grabbers and vdd
into PVCS, and test them. When we are satisfied that they work, we
should ship them with our driver, rather than relying on the ones
that Microsoft ships. This is also a better way to test and make
sure everything works.
Fixed By: evh
Date: 3-May-91
Fixed after version: 0.95
Fix:
Did it.
Modules affected:
Everything in r:\win3\vdd and r:\win3\gr3
Software Change Order
Windows 3.0 Driver
Date: Apr 25, 1991
Reported By: jlk
Found in Version: 0.92a
Priority (1,2 or 3): 3
Problem: Upon returning fromthe execution of XTNET system hangs. Use
O:\XTREENET\XTNET.PIF.
Fixed By: evh
Date: 6-May-91
Fixed after version: NF
This fails in VGA mode as well. It is probably a problem with xtnet.
(Note: Not all non-Windows apps work in the DOS box. They must be
'well-behaved.' There are certain things that can't be done like
writing directly to screen memory and mucking with interrupts. xtnet
is probably doing something with the network interrupt or int 2F.)
Fix:
Not fixeable.
Modules affected:
Software Change Order
Windows 3.0 Driver
Date: 3-May-91
Reported By: Dotti
Found in Version: 0.91
Priority (1,2 or 3): 2
Problem:
There is a problem highlighting text in PageMaker.
Fixed By: evh
Date: 10-Mar-91
Fixed after version: 0.95
Fix:
Our fancy 148 system color idea didn't fly. PageMaker expected 20
system colors - which is what the SDK specifies - and was downloading
its own palette. But since it was expecting 236 entries for its own
colors, and it only got 108, only the first 108 colors got loaded.
This through off their palette so the colors didn't complement any
more.
The GDIINFO structure in vga.asm was changed to revert to 20 system
colors and cool blue was added to the palette, and rgb_to_ipc was put
back into its original form with the exception that I added cool blue
so that it wouldn't be dithered.
Modules affected:
vga.asm
rgb2ipc.asm
Software Change Order
Windows 3.0 Driver
Date: 3-May-91
Reported By: evh
Found in Version: 0.95
Priority (1,2 or 3): 1
Problem:
In CorelDraw, you can specify that geometric objects are filled with
a bitmap. You select the paint can which pulls up a 'flyout' menu.
Then you select the bitmap icon (which is the fifth on from the left
on the top row of the flyout menu). Select a bitmap, and then try
drawing a rectangle. CorelDraw will hang.
Fixed By: evh
Date: 7-May-91
Fixed after version: 0.95
Fix:
I didn't quite get the last fix right. The call to BeginScanToDevice
was in the right place originally, the problem was that the jump went
to the wrong place. Instead of changing the jump, I moved the call.
This trashed some of the structure initialization necessary for
writing to in-memory bitmaps. I moved the call to BeginScanToDevice
back where it belonged, and changed the jump.
Modules affected:
ScanLine.asm
Software Change Order
Windows 3.0 Driver
Date: Apr 22, 1991
Reported By: jlk
Found in Version: 0.92
Priority (1,2 or 3): 3
Problem:
Entire screen flooded white. Running Winterm, performing
connection. Application text showed on top of white. Clock icon
reappeared when the minute rolled over. Clicking on area where
buttons should have been brought window back. Various other areas
returned to normal display by clicking on them.
Fixed By: evh
Date: 7-May-91
Fixed after version: NF
Fix:
According to John, he can no longer reproduce this bug.
Modules affected:
None.
Software Change Order
Windows 3.0 Driver
Date: 29-April-91
Reported By: evh
Found in Version: 0.95
Priority (1,2 or 3): 2
Problem:
UpdateColors uses block reads. It should use the host interface.
Sclr_dev uses block reads, Scandev uses block writes.
Fixed By: MJB
Date: 5/7/91
Fixed after version: .95
Fix: Added ifdefs for non-xseries boards; added cursor_exclude before
reading or writing through host interface.
Modules affected:
Trn_pal.asm, scandev.asm, sclr_dev.asm, cursors.asm.
Software Change Order
Windows 3.0 Driver
Date: Apr 25, 1991
Reported By: jlk
Found in Version: 0.92a
Priority (1,2 or 3): 1 (Man cannot live without R&R)
Problem: KaleidoKubes comes up in shades of grey rather than basic
primary colors (Red, Blue, Green Yellow). Execute
Q:\GENERAL\WIN3\GAMES\KUBES\KUBES3.EXE to replicate problem.
Fixed By: evh
Date: 7-May-91
Fixed after version: NF
Fix:
This is a bug in KaleidoKubes. They never pass down any colors but
black and white.
Modules affected:
None.
Software Change Order
Windows 3.0 Driver
Date: 5/7/91
Reported By: MJB
Found in Version: .95
Priority (1,2 or 3): 2
Problem:
Entering text in a "box" in Excel: When box full, enter another char,
the characters are redisplayed squeezed but the box wasn't cleared
first.
Fixed By: evh
Date: 10-May-91
Fixed after version: 0.95
Fix:
It is possible for the drawmode structure to specify transparent
drawing when there is an opaque rectangle. In these cases -
apparently - the flag in the drawmode structure must be over-ridden
and opaque text must be drawn.
Modules affected:
SBValGet.asm
Software Change Order
Windows 3.0 Driver
Date: May 21, 1991
Reported By: Jim Carroll
Found in Version: 0.98
Priority (1,2 or 3): 1
Problem:
Complete hang in corel draw. After: pen.. pen.. Arrows.. OK It just
stops. No keyboard, no mouse, no screen change.
Fixed By: evh
Date: 22-May-91
Fixed after version: 0.98
Fix:
In BBBufWr when blting a huge bitmap to the screen, we were bumping
the segment address before testing to see if we were done with the
blt, i.e., a pre-increment. This cause the segment address in some
cases to be incremented to an illegal value, which in protected mode
caused a protection violation. The end-of-loop test was moved before
the segment increment so this can't happen.
Modules affected:
BBBufWr.asm
Software Change Order
Windows 3.0 Driver
Date: 5/22/91
Reported By: Paul Angstman
Found in Version: .98
Priority (1,2 or 3): 1
Problem: Pull down FILE; select "manage publication"; choose "make TOC";
Select "cancel". The popdown will restore then you will be
hungski.
Fixed By: evh
Date: 23-May-91
Fixed after version: 0.98
Fix:
Same as sco 0056.
Modules affected:
BBBufWr.asm
Software Change Order
Windows 3.0 Driver
Date: 5/23/91
Reported By: Jeff Sweeny
Found in Version: .98
Priority (1,2 or 3): 1 - Fails install
Problem: Installing Windows on 3-1/2" disks, drive b:...Select other...
insert driver disk...reads disk once then looks to drive a: for the
disk again....Even when using the DOS assign command and make the
3-1/2" drive the a: drive this happens. Windows 3-1/2" disks install
fine for the default configuration.
Fixed By: evh
Date: 23-May-91
Fixed after version: 0.98
Fix:
This was a bug in the oemsetup file for 3 1/2" disks. For some
reason the bug didn't exist in the 5 1/4" oemsetup file.
Modules affected:
oemsetup.350
KNOWN BUGS
Software Anomaly Report
Windows 3.0 Driver
Date: 4-Apr-91
Reported By: evh
Found in Version: 0.91
Priority (1,2 or 3): 3
Problem:
When using Codeview, the cursor sometimes locks up, and this
sometimes crashes my system. I think it is the switching back and
forth between the Codeview block cursor on the monochrome screen and
the Windows cursor. (We may run into this same problem in the DOS
box.)
More info: The mouse cursor seems to work fine as long as you don't use
the mouse to pull down menu items in Codeview.
Later:
The bug has changed after version 0.92. It no longer crashes the
system, and the cursor no longer locks up in Windows. However, what
still happens is that when you switch to Codeview, the Windows cursor
is still active. You can move the cursor in Codeview and it still
moves in Windows. When you return to Windowws the cursor acts like
button 1 is being held down perpetually. You can reproduce this as
follows:
1) Invoke Codeview
2) Run an app
3) Once the app is loaded set a breakpoint in Codeview
4) Run the app until you hit the breakpoint
5) Use the mouse in Codeview to pull down a menu. You
will see the Windows cursor still active.
6) Switch back to Windows and move the cursor over the menu
bar. Without pushing the mouse button, menus will
be pulled down. Pushing the mouse button once ends
this behavior.
What is probably happening is that the mouse isn't being disabled,
and the last mouse down event is being process by Windows instead of
Codeview.
Even later:
Here is a guess. The grabbers probably need to shut down the cursor.
This bug could take quite a while to fix. I think it can wait.
Still even more laterer:
Yep. The grabbers have cursor code. This is probably it. Also
notice that the VGA driver actually removes the cursor from the
screen while in Codeview, and then puts it back up when you switch
back to Windows.
Software Anomaly Report
Windows 3.0 Driver
Date:April 18
Reported By: Dotti
Found in Version:All
Priority (1,2 or 3): 2
Problem:
Text gets "caught" in Toolbox of PageMaker 4.0 when doing flip
screens.
Software Anomaly Report
Windows 3.0 Driver
Date: 10-April-91
Reported By: JLK
Found in Version: 0.92
Priority (1,2 or 3): 3
Problem:
This morning I tried running the Elite at 800x600 res and everything
came up smoothly.
The only issue I have encountered is with the size of the window bars
and the type used there. Both the bars and the type are larger than
those used in 800x600 VGA.
(This is a general problem with the driver. The screen metrics are
all set up for 1024 x 768. It runs ok, but it doesn't always look
very good. We may need a separate 600 x 800 driver, or we need to
change Enable to return the correct metrics in the GDIINFO structure
when running at 600 x 800. This needs some exploration. To some
extent it depends on how many people out there really need/use 600 x
800.- evh)
Software Anomaly Report
Windows 3.0 Driver
Date: 5/07/91
Reported By: MJB
Found in Version: .95
Priority (1,2 or 3): 3
Problem: Paintbrush in black and white mode. If you fill screen with a
mostly black pattern (scanlines with a brush), then try to fill
with black, it takes forever to finish whatever it does and
doesn't change anything. Should repaint the screen black.
Software Anomaly Report
Windows 3.0 Driver
Date: Apr 22, 1991
Reported By: jlk
Found in Version: 0.92
Priority (1,2 or 3): 3
Problem:
Can't print on local printer from Notepad or eMAIL. WORD works
fine. Apps work under 800x600 VGA OKay. Running 800x600 in 386enh
mode.
Fixed By: Nada. Tested by MJB
Date: 5/6/91
Fixed after version: .95
Fix: Tested with both resolutions on my local printer.
Operator error.
Software Anomaly Report
Windows 3.0 Driver
Date: 20-May-91
Reported By: Dotti
Found in Version: 0.95
Priority (1,2 or 3): 1
Problem:
Power Point hangs when running a slide show.
Software Anomaly Report
Windows 3.0 Driver
Date: 5/22/91
Reported By: Paul Angstman
Found in Version: .98
Priority (1,2 or 3): 3
Problem: In Paintbrush -- select text; put in several characters; change the
size of the text to something 64 or larger. The previously typed
text is clipped on the bottom, but new text entered is okey dokey.
Software Anomaly Report
Windows 3.0 Driver
Date: 5/22/91
Reported By: Paul Angstman
Found in Version: .98
Priority (1,2 or 3): 2
Problem: In Ventura -- use the toolbox in the upper right corner of the
window to draw a rectangle, circle, and rounded rectangle. Pull
down the graphics menu; select "select all"; pull down the
graphics menu; select "fill attributes"; pick a pattern.
The rectangle fills OK, but the rounded rectangle and circle do NOT
fill properly (usually white, but I did see solid color fills too).
Software Anomaly Report
Windows 3.0 Driver
Date: 5/23/91
Reported By: Jeff Sweeny
Found in Version: .98
Priority (1,2 or 3): 3 - BMP files don't display properly.
Problem: Follow these steps...Select control panel...Desktop...change
the wallpaper pattern. If you select a BMP file that is a scanned in
photograph it will be displayed but the pallette is all screwed up.
Exit windows 3.0 then go back in and the colors look fine.