🚀 go-pugleaf

This is my first attempt at posting on Usenet, although I've been perusing
the news for some time, so feel free to correct any glaring lapses in
netiquette or give me suggestions for more appropriate groups to post the
following info to.

The Problem;

I am unable to run 'win /3' after loading SCO Unix 3.2v4 onto a separate
disk partition. The Windows logo displays and a few scattered pixels show
up after the logo clears, but I am always returned to the dos prompt.

Configuration: Acer 1133E with 210Mg HD, ATI 1024 Video, 16 Meg Ram.

DOS 5.0 was loaded first, followed by Windows 3.1. At this point, Windows
ran in either standard or 386 Enhanced mode. The problem does not show up
until SCO Unix is loaded and is located onto a partition which occupies the
remainder of the disk.

I contacted MicroSoft support and they were fairly helpful, but we could
come to no resolution (they even found a couple of other reports, but there
was no resolution in either of those reported instances; customer may have
given up or solved it and not called back).

I also tried all the troubleshooting techniques contained in the last issue
of the Windows Resource Kit for 3.1 to no avail.

Manually changing the active boot partition back and forth between Unix and
DOS has no effect.

In fact, the ONLY thing that seems to make a difference is to use DOS fdisk
to remove the Unix partition. 'win /3' then starts working again, but I've
lost Unix at that point.

I've been unable to get through to SCO Support or access the SOSCO BBS (no
contract support), so if anyone else has access and knows if this has
already been reported to them and has seen a relevent 'it script', I'd be
thrilled to find out what's going on. I hate to have to make a choice between
crippling the full functionality of Windows or abandoning Unix. If you'd like
to reply by private e-mail, my mail address is 'mferreri@altos.com'.

Thanks-In-Advance