Windows v3.00 bug report #1 - 6/4/90
Reported by Kim Levitt, Synergisitic Enterprises

1) When copying over a file using the file manager, the directory display
is not updated. (i.e. I copied WIN.INI to WIN.SAV, system prompts me, OK
to replace WIN.SAV, I say yes, it copies file, but directory entry for new
WIN.SAV is not updated. Have to use refresh to update directory entry for
the new file.)

2) When deleting several files, the constant updating of the directory
display as each file is deleted is very annoying. How about just updating
the display after all the files are deleted or moved?

3) SMARTDRV has serious problems. I have a system with 2 ST277R-1 RLL 65MB
disk drives that operate off one controller. The number of sectors per
track with RLL drives is 26, (not the standard 17). Unfortunately, the
CMOS/BIOS setup on my machine does not include RLL type drives (many
systems don't). This means the BIOS reports 17 sectors and the disk is
actually 26. Normally this is not a problem. HOWEVER, SMARTDRV apparently
gets "confused" (not sure if the BIOS vs. Boot sector is the problem) and
occassionally I was getting "sector not found errors". Warm booting would
reset things and all would be well again, but obviously I couldn't run
SMARTDRV and have it scramble my hard drive. (I should add that only the
SECOND physical hard disk (drives D: and F:) was affected... These bugs
existed in previous versions of SMARTDRV, although the symptoms are
slightly different now. (The earlier version would lose the directory for
drives D: and F: completely, now I just get sector not found errors.)
Until SMARTDRV can be fixed, I have purchase Super PC-Kwik, an excellent
disk caching program. I should add that Super PC-Kwik recognizes the
difference between the BIOS settings and boot sector settings and uses the
boot sector numbers... It seems to be working fine and I have had no
problems since I dumped SMARTDRV.

4) When I first tried running Windows in 386 mode on my system, it would
simply crash (with no error message). I believe the problem was a lack of
disk space for the 386 swap file, as when I later managed to free up more
disk space, it worked fine. It would be nice to give an error message
instead of just crashing.

Well, that's all for now. As I use Win3 more, I am sure I will find some
other problems, and I will issue bug reports if I do... MICROSOFT PLEASE
TAKE NOTE AND FIX THESE BUGS!

If you want to contact me, call my BBS system at (213) 653-6398 and leave
a comment.

						--- Mr. Kim Levitt
						    Synergistic Enterprises

P.S. I do like the solitaire game, only problem with it is it's so
addictive!
                                                                                                                       