Tried implanting Windows 98's setup program in here during 95D development.
It sort of worked but failed on the first boot due to essential drivers not being loaded.
Ruby: Well, that's really only for the original release of Windows 95 and accompanying first party software titles. Later versions of 95 would switch to the XXXXX-OEM-XXXXXXX-XXXXX format - which was more complex, though it was mainly intended for OEMs to use as part of the key implies. Actually, the number of characters for each block outside of the OEM part is also the exact number of syllables used in haikus (5, 7, 5).
Really funny how you can use 111-1111111 as a key in Windows 95 and it works.
Thank you for the explaination. Shame that it turned out like that - it would give a lot more room for modularity in custom Win9x distributions.
Windows 95's SETUPX.DLL file is limited in the number of individual optional components it can load, at most 60 to 63. I wanted to add in more optional components for things like desktop themes, but this causes the program to crash. Windows 98 raises the limit by a lot, hence more optional components are available. This could also be the reason why Windows 98 displays a "Please wait" dialog when you click the Windows Setup tab in Add/Remove Programs as it loads a list of components, while Windows 95 does not.
We initially tried to transplant multiple files into 95D to combine the best of the whole series together, which turned out to be messy in the end of it - which is why 95D Lite doesn't have any of the Memphis stuff unless otherwise provided manually.
What would be the benefit of that?
7 comments on this page
Sort: Ascending | Descending
Leave a Comment