Petr

It seems you have problems to understand what was written in this and other threads.There were given many strong reasons why to use Win9x and many strong reasons why not to use it, it is always depending on your existing hardware, existing applications and personal preferences. If the reason that specific hardware or specific software does not work with NT based systems is not "one good reason" for you - then there is nothing to discuss. My opinion is different - I understood that DukeBlazingstix wrote this becasue he wanted to express that he wants really to listen and discuss, not just start a flamewar like some other people (Link21 and you) often do. Please also keep in mind that people just have personal preferences and most discsussions like "What is better - ATI or Nvidia? AMD or Intel? Western or Seagate? Gigabyte or Asus? Firefox or Opera? Windows or Mac or Linux? Mercedes or BMW?" are mixed with 1% of technical things and 99% of personal opinion. Not respecting this fact and not respecting other people opinion leads just to flamewar, nothing else can be the result. Petr

As I mentioned several times, there is no Win9x support for USB2.0 in Intel ICH6, ICH7 and ICH8 southbridges. The newest Orangeware driver I know is here: http://old.winpack.org/petr/U2v242.exe but it supports ICH4 only. There are universal EHCI (USB2.0) drivers for DOS, Windows NT 4.0, Windows 2000 and newer - but none for Win9x, all are bound to specific PCI IDs. Petr

OK, it is here: http://old.winpack.org/petr/SHELL32-ITA.zip Petr

Yes, it seems the "Anonymous author" made some mistake. I just tried to load this file by Heaventools PE Explorer (not free), saved it, the size has decreased and Restorator works fine. The best would be if MDGx could ask "Anonymous author" to repair the shell32.dll file, I'm not sure that shell32.dll repaired by PE Explorer is 100% functional (I have not tested it) Petr Edit: I have tried to use shell32.dll patched by "Anonymous author", re-saved by PE Explorer and all resources replaced by Czech resources by Restorator and the system booted and did not crashed (yet). No deep testing.

See my posts: Localization of SP 2.0 SED, INF, DDF file format description (and others) Petr

I have similar problem but in one special case only. Copying from Windows XP to Windows 98 - normal speed Copying from Windows 98 to Windows XP initiated on Windows 98 - normal speed Copying from Windows 98 to Windows XP initiated on Windows XP - very slow speed I never found any solution. Petr

Irony or mistake? You may guess... Corrected. Petr

As Drugwash reported here @ Dec 12 2006, 12:58 PM RichEdit 4.0 riched20.dll (5.40.11.2218) has problem with somer applications, like eMule (not clickable link) or Miranda IM spellchecker (spelling errors not underlined). I don't know how to use Miranda IM but I have installed eMule and the link is really not clickable with riched20.dll 5.40.11.2218. Both Miranda IM and eMule are open source but I'm not a programmer so I cannot guess if the code can be modified to work with all riched20.dll versions. It is not an issue for Windows language version that use US-ASCII 1252 codepage but for other language versions it is real problem, there are many applications that exhibit unwanted font switching with RichEdit 3.0 and RichEdit 4.0 is solution for this problem. Exactly the same situation is on all operating systems till Windows XP and Vista. It is possible to place the right version of riched20.dll to the application folder and so far it seems to be the only possible solution. Maybe somebody could be able to patch RichEdit 3.0 riched20.dll to correct the font switching bug? Petr

I'd like to move the riched20 discussion to the proper topic: RICHED20.DLL compatibility Petr

note: RichEdit 6.0 (12.0.4017.1003) does not work on Win9x - there is unresolved dependency to GetGlyphIndicesW in GDI32.DLL

Really? That's very bad, Riched20.dll 4.0 (5.40.x.x) is required for Metapad and many other programs to work with non-ASCII codepages, like East/Central European codepage 1250. This topic was alaredy discussed here: http://www.msfn.org/board/index.php?showtopic=72448 and the conclusion was that it is safe to use riched20.dll version 5.40.11.2218 because it does not break anything. Here you can see the difference: Richedit 3.0 (all versions): Richedit 4.0 (all versions): This is also noted here: http://www.liquidninja.com/metapad/faq.html#Q18 This problem si common for Windows 98, Windows Me, Windows 2000, Windows XP, Windows Server 2003 and even Windows Vista. Therefore I have opened the incident # SRQ060526601424 with Microsoft and asked them to correct this bug but after several months of e-mailing and phone calls the result was: So Microsoft will not correct any bug without "business impact plan", even if you have paid for the support. Very polite response - but nothing was done yet, even the bug was not documented in MSKB yet. Back to RICHED20.DLL. Are you able to document your problems with Richedit 4.0 and Miranda? I don't use Miranda so I'd like to test them. The serious problem with Richedit 3.0 and 3.1 and Windows with default codepage 1250 (defualt in Czech, Hungarian, Polish, Slovak, Slovenian versions of Windows 98) has to be solved some way. Maybe there is some other workaround? Or someone will be able to patch riched20.dll 3.0? My understanding is so that Richedit does a test if the character is supported in the currently selected font. If it is missing, then it switches to different font that contains it - just to be able to display the character and not empty rectangle only. Unfortunately there is a bug in Richedit 3.0, 3.1 and even 5.0 that causes font switching even when the character is supported by the currently selected font. Regards, Petr

The version number is stored as four 16-bit words, each part of it may have value 0 to 65535. So the lowest version number is 0.0.0.0 and the highest 65535.65535.65535.65535. Some more information from MSDN: VS_FIXEDFILEINFO Structure File Version Comparisons Codeguru: Versioning in Windows Petr

Just FYI - the above mentioned entries are for AGP versions of those boards only. Petr

Unfortunately ESDI_506.PDR does not work with SATA controllers in native mode. Tested with Intel and VIA chipsets and I suppose it is the same for all others. Maybe the required modification of ESDI_506.PDR is not big because the software interface to the drive should be really the same. Petr

AFAIK Virtual PC 2007 is still beta and available to beta testers only. Link to Connect. Free download is for Virtual PC 2004 with SP1 and Virtual Server 2005 R2 Enterprise Edition. Petr

There is no Win9x driver for SATA and Audio. Apparently there is Win9x LAN driver.

There is a European Union Expansion Font Update Updated versions of Times New Roman (regular, bold, italic and bold italic), Arial (regular, bold, italic and bold italic) and Verdana (regular, bold, italic and bold italic) that include six additional characters not available in the Windows XP versions of these fonts. The new added characters are Unicode code-points U+0218, U+0219, U+021A and U+021B used for Romanian and U+040D and U+045D used in Bulgarian. It should install on Windows 95 to Windows Vista.

Yes, it has Save as PDF function and it works very well. Petr

I use pdfFactory - is very good but not free and not open source.

Who "could just use Windows 2000"? Windows 2000 is not freeware, you have to pay $219 or $199 for the license (official upgrade price from Microsoft for W2000 and for WXP respectively). (not mentioning how slooooow Windows 2000 is and that the mainstream support was already discontinued by Microsoft) Petr

These seems to be no Win9x support for ATI® RADEON XPRESS 200 chipset - as you can see here: http://www.ecs.com.tw/ECSWeb/Downloads/Pro...=35&LanID=0 Petr

Fully supported are chips 865/875, from Asus P5PE-VM with Core2 Duo support is available. But this board has AGP, not PCI-E. P5LD2 SE (PCB R2.0+) with 945P chipset support Core2 Duo processor too and has PCI-E slot, but the compatibility with Windows 98/Me is very limited. Petr

Please see where it is placed - it is in HKLM,"Software\Microsoft\Windows\CurrentVersion\Time Zones" key, not in HKLM,"Software\Microsoft\Windows\CurrentVersion\Time Zones\Dateline". It seems that HKLM,"Software\Microsoft\Windows\CurrentVersion\Time Zones" contains default time zone for given language version of Windows 98, English version contains "Pacific Standard Time". Petr

Hello, I've received very interesting information from local office of Microsoft (both in written and oral form): Windows 98 (4.10.1998) license entitles the license owner to use Windows 98 SE (4.10.2222) too. Legally bought media (CD-ROM) must be used, so you can either use the CD-ROM that you already bought for other computer, or you can ask Microsoft Fullfillment Service for new one (for administrative fee). Is anybody able to verify if this is opinion of the whole Microsoft or just our local office only? Petr

Does anybody know if this fix: KB928939 Western Australian Daylight Savings Changes for Microsoft Windows for the Year 2006/2007 is already contained in 928388 or not?