Re: Windows Resource Limits (was Re: Pathfinding)

[Eric McDonald <mcdonald at phy dot cmich dot edu>]

On Fri, 2004-05-07 at 10:33, Eric McDonald wrote:
> On Fri, 7 May 2004, Hans Ronne wrote:
> 
> > Well, the GDI limit exists also in 98 and ME, so you don't need 95 to test
> > that. 
> 
> Right. It's just that I don't own 98, 98SE, or ME (thankfully).
> 
> >But it would be nice to know if xconq runs at all on 95. I never
> > tested it. Maybe somebody on the list did?
> 
> We'll find out soon enough.... I think you asked about whether 
> anyone ran it on 95 before, and no one spoke up.

Well, I finally got Win 95 going inside a virtual machine. It took me
all afternoon and part of the morning to scrounge up enough pieces of
DOS from various partially decayed disks ("abort, retry, ignore" was the
story) to get COMMAND, FDISK, EDIT, and FORMAT all on one booting disk.
Then, a while longer to get MSCDEX and a generic ATAPI CD-ROM driver on
the newly formatted virtual harddisk, so that I could load the Win95
CD-ROM.... Once that was done though, the Win95 install blazed by.

I then copied over my latest Xconq installer. The installation went
flawlessly. Unfortunately, Tk84.dll relies on a newer COMCTL32 DLL than
what comes with stock Windows 95. Bundling a newer version of COMCTL32
will probably not help since it likely has dependencies on other newer
things (KERNEL32, perhaps). I am tempted to write Windows 95 off as an
unsupported platform.... However, it may be that the service pack or a
newer IE will upgrade the necessary components, so as to make a patched
Windows 95 usable by Xconq.

I may muck with this tomorrow. I've had enough mucking around with
Mordorsoft products for the day (though I may dd an image of my working
DOS disk to my HD so that I never have to waste an afternoon dealing
with the DiOSpora again).

Eric

P.S. Hans: Instead of a low resolution Xconq icon showing up on the
desktop, the generic Windows executable icon appears instead. (I also
see this with MinGW32-linked Xconq executables.) I will scrutinize the
installer script to see if there is something it is doing wrong when it
creates the shortcuts, but I still suspect the problem is somewhere in
the linkage.