Platform<=>version conflict or what?

[Jorma Paavola]

Hi Phil,

I reply on this and separately to your mail sent on 3.7, which I 
unfortunately found recently from "Junk-box"-
 > Hi Jorma,
 >
 > My copy of Win98 (SE) is:
 > Operating System:       Microsoft Windows 98 (32-bit)
 > OS Version:     4.10.2222 A (Second Edition)
 > (all critical updates have been installed.)
 >
 > DW reports your version as:
 > Operating System:       Microsoft Windows 98 (32-bit)
 > OS Version:     4.10.1998 (Gold)
 >
 > So we are running different O/S versions.

Yes , we are using different Win98 versions.
My "basic" Win98 has been automatically updated since beginning and is 
certainly including the latest updates intended for this version

Your SE (second edition) is a bit higher class version of it. I know, I 
could upgrade my "basic" Win98 into SE-version, which I however don´t 
want due my use it as testing-bench only for possible incombitibility 
problems of Win9x-OS´s.


 > And most of any development interest will probably be focused in on 
areas where
 > the market share is advancing,  not declining.
 >
 > Not to say that it can't be made to work under Win 98.  Just a matter of
 > how much time one is willing to invest in making it go.

Win98 is not supported by Microsoft anymore, but due the simplicity and 
certain weaknesses it is still a good test-bench !
 >
 >> - the use of totally failing child-module of USERENV.DLL is NTTDL.DLL
 >> which (on my Win98 is original one and dated 1998 !) possible should be
 >> reconsidered (substituted or delay-loaded or?)or updated with a newer
 >> version (as the case is on Win2k !)

NOTE: the correct name for problematic failing module is NTDLL.DLL not 
(NTTDL.DLL as above !) Sorry for printing error !

The precense of this module on loading-table of sw on Win98 has started 
to worry me more because:
- this module is intended for NT-handler, which is used in PC´s with 
NT-filesystem as Win2k and above !
- My sw is originally made on Win2k
- I guess, that this part of preparing the "running environment" for 
application on Win98 simply fails already before (due handling problems 
of NTDLL.DLL) it is starting to handle application itselves (starting 
from _core_.pyd), if sw has to be unpacked as bundled or NSISed !!?
- unfortunately I don´t know if that part of python could be reorgasised 
such way(f.ex delay-loaded), that use NTDDL.DLL-module could be avoided

Some comments ?

Jorma