Petr

So the Misumi USB Floppy drive works well on freshly installed Windows ME. I have compared registers and nothing very special found. Here are some differences but I don't know what they mean - if anything: Win98 SE + nusb2.2 [HKEY_LOCAL_MACHINE\Enum\USBSTOR\SFLOPPY&VEN_MITSUMI&PROD_USB_FDD&REV_1050\USB&VID_03EE&PID_6901&INST_0] "Capabilities"=hex:14,00,00,00 WinME: [HKEY_LOCAL_MACHINE\Enum\USBSTOR\SFLOPPY&VEN_MITSUMI&PROD_USB_FDD&REV_1050\USB&VID_03EE&PID_6901&INST_0] "Capabilities"=hex:00,00,00,00 Win98 SE + nusb2.2 [HKEY_DYN_DATA\Config Manager\Enum\C2A168E0] "HardWareKey"="USBSTOR\\SFLOPPY&VEN_MITSUMI&PROD_USB_FDD&REV_1050\\USB&VID_03EE&PID_6901&INST_0" "Problem"=hex:0b,00,00,00 WinME: [HKEY_DYN_DATA\Config Manager\Enum\C1C798F0] "HardWareKey"="USBSTOR\\SFLOPPY&VEN_MITSUMI&PROD_USB_FDD&REV_1050\\USB&VID_03EE&PID_6901&INST_0" "Problem"=hex:00,00,00,00 What to try next? Petr

I'm sorry, I forgot to look into the SED file. I just entered TargetWin9xVersion in Google and found one reference only - eGorZ's post on board.ru - nothing else. Petr

Maybe to add version check as suggested by eGo®Z on RU-BOARD half year ago for nusb project: при создании sfx-cabа в sed-файл в секцию [Options] добавь ручками строчки в самом конце -------- TargetWin9xVersion=4.10.2222 TargetNTVersion=4.10.2222 -------- и не нужно будет всех предупреждать о том что это только для winSE - в другое место просто не поставится I'm only not sure how these options work - they seems to be completely undocumented. Or didn't I catch something? It would be also very nice to be able to limit the installation to specific language version only too. Petr

It is absolutely different. Now I prepare installation of WinME. Petr

This is wrong. There are two different LBA modes - classic 28-bit and newer 48-bit., but both of them are LBA. Both old CHS addressing and newer LBA (28-bit) addressing use the same 28 bits, but in different manner. The rest what you wrote is correct, I just want to emphasize that 48-bit LBA is not the same as LBA. Petr

Yes, I have version 4.10.2223. With version 4.90.3000 windows won't boot.

The same BSOD on completely different configuration and the same Mitsumi floppy drive - ICH-2 USB, Czech version of Windows 98 SE. Any idea how to solve the problem? This floppy drive is explicilty written in the original Win ME INF file, so it should be supported. I will also try to install Windows ME to see if it really works. Petr

Hello Maximus, I have problems with this USB package and Mitsumi USB Floppy drive. The system is freshly installed Windows 98 SE + drivers + SE SP 2.0 RC3 + NUSB2.2, motherboard is i845 chipset with ICH-4 southbridge. When I insert this floppy into USB connector, at first looks like at least twe drivers are properly recognized, but then BSOD appears with message: A fatal Exception 00 has occured at 0028:C1C24DD4 in VXD DiskTSD(03) + 00011EB4 - the current application will be terminated. After reboot there is yellow exclamation mark at USB Floppy Disk in Storage devicess class in Device manager. If I remove the driver from device manager, an re-insert the USB connector, the blue screen appaered again. What is installed in registry: [HKEY_LOCAL_MACHINE\Enum\USB\VID_03EE&PID_6901\INST_0] "Capabilities"=hex:14,00,00,00 "HardwareID"="USB\\VID_03EE&PID_6901&REV_0100,USB\\VID_03EE&PID_6901" "CompatibleIDs"="USB\\CLASS_08&SUBCLASS_04&PROT_00,USB\\CLASS_08&SUBCLASS_04,USB\\CLASS_08" "DeviceDesc"="Mitsumi USB Floppy" "ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}" "Class"="USB" "Driver"="USB\\0013" "upperfilters"="USBNTMAP.SYS" "Mfg"="Microsoft" "ConfigFlags"=hex:00,00,00,00 "Serial"=hex:0c,00,00,00,00,00,00,00 "SymbolicName"="\\DosDevices\\000000000000000c#{a5dcbf10-6530-11d2-901f-00c04fb951ed}" [HKEY_LOCAL_MACHINE\Enum\USBSTOR\SFLOPPY&VEN_MITSUMI&PROD_USB_FDD&REV_1050\USB&VID_03EE&PID_6901&INST_0] "Capabilities"=hex:14,00,00,00 "HardwareID"="USBSTOR\\SFLOPPYMITSUMI_USB_FDD_________1050,USBSTOR\\SFLOPPYMITSUMI_USB_FDD_________,USBSTOR\\SFLOPPYMITSUMI_,USBSTOR\\MITSUMI_USB_FDD_________1,MITSUMI_USB_FDD_________1,USBSTOR\\GENSFLOPPY,GENSFLOPPY,USBSTOR\\SFLOPPY&VEN_MITSUMI&PROD_USB_FDD&REV_1050" "CompatibleIDs"="USBSTOR\\SFLOPPY,USBSTOR\\RAW" "DeviceDesc"="USB Floppy Disk" "Class"="Storage" "Driver"="Storage\\0004" "Mfg"="Generic" "ConfigFlags"=hex:00,00,00,00 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\USB\0013] "DevLoader"="*NTKERN" "NTMPDriver"="USBSTOR.SYS" "DriverFlags"=dword:00000002 "InfPath"="USBSTOR.INF" "InfSection"="USBSTOR_CBI" "ProviderName"="Microsoft" "DriverDate"=" 4-11-2005" "DriverDesc"="Mitsumi USB Floppy" "MatchingDeviceId"="USB\\VID_03EE&PID_6901" [HKEY_DYN_DATA\Config Manager\Enum\C29A52C0] "HardWareKey"="USB\\VID_03EE&PID_6901\\INST_0" "Problem"=hex:00,00,00,00 "Status"=hex:ce,6a,88,19 "Allocation"=hex:00,04,00,00,00,00,00,00,00,00,00,00 "Child"=hex:e0,68,a1,c2 "Sibling"=hex:00,00,00,00 "Parent"=hex:30,50,a1,c2 [HKEY_DYN_DATA\Config Manager\Enum\C2A168E0] "HardWareKey"="USBSTOR\\SFLOPPY&VEN_MITSUMI&PROD_USB_FDD&REV_1050\\USB&VID_03EE&PID_6901&INST_0" "Problem"=hex:0b,00,00,00 "Status"=hex:a6,6e,00,18 "Allocation"=hex:00,04,00,00,00,00,00,00,00,00,00,00 "Child"=hex:00,00,00,00 "Sibling"=hex:00,00,00,00 "Parent"=hex:c0,52,9a,c2 With Windows XP and with Mitsumi supplied driver and Windows 98 SE everything works without any problems. Also several various USB flashdisks works fine with NUSB2.2 on the same computer. Any idea? Petr

May I know what does the modification of WINBOOT.SYS? There are changed bytes at address 136C2 04 -> 03 and 136D5 74 EE -> 90 90. Are there any other modified files? Petr

That's OK, I was not sure what is the origin for some files because you had different KB number in the INF file than is the hotfix package available (if any). Filelist for dun14, dsclient and other packages have its KB number too. I believe :-) I wanted to summarize what I found because I forgot one string in my previous post. Petr

And what about Q307004 http://support.microsoft.com/?id=307004 ? It is available and it is for Windows 98 SE. http://www2.tw.freebsd.org/cpatch/msupdate.../307004usa8.exe Date Time Size File name Operating system ------------------------------------------------------------------- 09-Oct-2001 14:20 11,264 Grouppol.dll Windows 98 09-Oct-2001 13:31 11,264 Grouppol.dll Windows 98 Second Edition And what about Q230766 http://support.microsoft.com/?kbid=230766 ? It is not available and it is for Windows 98 SE. Date Time Version Size File name ------------------------------------------------- 04/30/99 3:56pm 4.10.0.2223 8,704 Ksolay.ax 04/30/99 3:48pm 4.10.0.2223 126,976 Ksproxy.ax 04/30/99 4:15pm 4.10.0.2223 39,808 Stream.sys And what about Q243174 http://support.microsoft.com/?kbid=243174 It is not available and it is for Windows 98 SE. Date Time Version Size File name Platform ------------------------------------------------------------------ 30-Sep-1999 15:31 4.10.2224 54,944 Msdv.sys Windows 98 SE 14-Jul-1999 11:54 6.1.5.319 187,488 Qcap.dll Windows 98 SE 11-Feb-2000 15:56 6.2.10.1 216,336 Qdv.dll Windows 98 SE Petr

One question regarding strong/weak cryptography. In the Service Pack are the following files: SECUR32.DLL - Microsoft Win32 Security Services (Export Version) SCHANNEL.DLL - TLS / SSL Security Provider (US and Canada Use Only) RSAENH.DLL - Microsoft Enhanced Cryptographic Provider (US/Canada Only, Not for Export) The export restrictions were relaxed several years ago, so it is not the problem, but is there also SECUR32.SLL with strong cryptography? Petr

Hi Gape, I have checked comments in the main INF file and here are some possible changes: Disktsd.vxd ;246387 Hh.exe ;W2003 SP1 Regtlib.exe ;oainst - IE6.0SP1 Hhctrlui ;W2003 SP1 Sysdm.cpl ;272620, 272621 Cabinet.dll ;InstMSIA Vpowerd.vxd ;246817, 246615 Rsaenh.dll ;iedom - IE6.0SP1 Enhsig.dll ;iedom - IE6.0SP1 Hhctrl.ocx ;W2003 SP1 Hhsetup.dll ;W2003 SP1 Itircl.dll ;W2003 SP1 Itss.dll ;W2003 SP1 Asycfilt.dll ;W2000 SP4 Oleaut32.dll ;W2000 SP4 Olepro32.dll ;W2000 SP4 Stdole2.rlb ;W2000 SP4 Regsvr32.exe ;W2000 Msvbvm60.dll ;vbrun60 Ndis.vxd ;270063 Kbdhid.vxd ;245065, 242928 Mouhid.vxd ;Intellipoint 4.12 Vnbt.386 ;269239, 264650 Pppmac.vxd; DUN14 Msnet32.dll ;dsclient 323455 Sens.dll ;IE5.5SP2 Maybe you will correct me. Please also move to "Localizable strings" section: "0409" LCID "EN" locales "Show Attributes in Detail View" text "Registering " texts to make localization easier. Petr

And another idea - many countries has changed the telephone dialing system since release of Windows 98 so it would be good to correct the registry entries. Changes in the Czech Republic are described in http://support.microsoft.com/kb/327517 and the new registry entry is: [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Telephony\Country List\420] "LongDistanceRule"="G" Here it is described also for Greece: http://support.microsoft.com/kb/750109 Petr

Hi Gape, regarding QFE registry entries, I have read your half year old discussin where you described that it is not easy to put registry entries just for files actually installed. If added the possibility that files can be installed also later by the preserving mechanism, it is almost impossible I think. I suggest an easy way - just put to the registry everything, for all files, even for those without QFE special build version, and QFECheck tool can be used to see if any files from the Service Pack were overwrittedn accidentaly by some older version or not. It means that in the documentations would be written that "Missing File" is no error. It is better than nothing and it would enable everybody to see that all files are correctly updated. What do you think? I will send you the sample of such file by e-mail. Petr

Good idea, but hard to find the right layout. It would be good to add what files are contained in the update/hotfix and which of them are obsoleted by a newer version - not always the whole package is replaced by new one. I'd also add the information if the file is available on Windows Update, and if it is classified as "Critical Update". Also Microsoft Security Bulletin numbers could be added (MS05-001 and similar). And the information what are known differences besides of the differences described in the knowledgebase. For example new sysdm.cpl does not display CPU type. To achieve several differen views, it would be good to build it as application, not as static web page. Unfortunately it would need much time. I will send you my tables directly, maybe you will find something useful. I'm not sure if it can be easily mark files as "multilanguage", or maybe better as "localized" or "localizable". It depends on the language sometimes, some files are translated only to about 8 languages (German, Japanese, etc.) but not to all of them. I have a table what KB files are localized in Czech version of Windows 98 and 98 SE so I can compare your knowledge. In fact, the only real multilanguage file is msdapml.dll, it contains 35 Locale IDs. There are also problems with files that seems to be localized, but are not. The best known example is WINBOOT.SYS in 311561CZE8 is US ENGLISH version of the file and it has problems in Czech Windows 98 - Yes/No replies are not localized as applications like FDISK or FORMAT expect. Petr

So I played with Proxomitron and things are really strange. All versions of IE seems to use the first request at address http://www.microsoft.com/isapi/redir.dll?p...&os={SUB_OSVER}, where: {SUB_PRD} = ie {SUB_CLSID} = Locale ID, i.e. 0x0409 for US English, 0x0407 for German, 0x0405 for Czech etc. {SUB_PVER} = 5.0 for IE 5.0, 6.0 for IE 6.0 (SP1) {SUB_OSVER} = 98 for Windows 98 (SE) So for US English IE 5.0 the request is: http://www.microsoft.com/isapi/redir.dll?p...ar=ienews&os=98 and the response from Microsoft is redirection to the fillowing pages (for Locale ID 0401 to 0420): 0401, 0402, 0403, 0404, 0407, 0409, 040d, 040f, 0411, 0417, 0418, 041b, 041c http://windowsupdate.microsoft.com/default...=productupdates 0406, 0408, 040a, 040b, 040c, 040e, 0410, 0412, 0413, 0414, 0415, 0416, 0419, 041a, 041d http://windowsupdate.microsoft.com 0405 (Czech): http://www.microsoft.com/windows/ie_intl/cs/ Both http://windowsupdate.microsoft.com/default...=productupdates and http://windowsupdate.microsoft.com is redirected to http://v4.windowsupdate.microsoft.com/ - real Windows Update site. Just for Czech Locale ID it goes to different place. For US English IE 6.0 SP1 the request is: http://www.microsoft.com/isapi/redir.dll?p...ar=ienews&os=98 The redrection for all locales is to http://windowsupdate.microsoft.com/ - again with exception of locale 0405 (Czech) which redirects directly to http://v4.windowsupdate.microsoft.com/cs/default.asp So the problem exists just for 0405 Czech locale (at least from 32 locales tested) and iis caused by wrong setting of the Microsoft server. I will try to solve it with Microsoft, and if necesary, in Czech localization of SP 2.0. Sorry for suggesting bad idea. Petr

Thank you very much, I have added them recently and did not so good search for them. So now are remaining: Q192112 Kswdmcap.ax, Vfwwdm.drv, Vfwwdm32.dll 4.10.2043 (only if this is really newer version than vfwupd.exe 4.10.2000 with newer date) Q192117 Mstcp.dll 4.10.2012 Q196527 Dvdplay.exe Q222902 Ntkern.vxd 4.10.2103 Q224073 Vcache.vxd 4.10.2183 Q230791 1394bus.sys, Ohci1394.sys 4.10.2179 (I know that IEEE1394 support on Windows 98 Sandard Edition is not perfect) Q243048 Apmbatt.sys 4.10.1999 Q254087 Vmm.vxd 4.10.2000 Q265528 Vnetbios.vxd 4.10.2223 (Really is this version not suitable for SE??) Q323708 Nscirda.sys 4.10.1999 Petr

So at present, it seems that only the following hotfixes are missing: (thanks erpdude8) Q192112 Kswdmcap.ax, Vfwwdm.drv, Vfwwdm32.dll 4.10.2043 Q192117 Mstcp.dll 4.10.2012 Q196527 Dvdplay.exe Q209321 Dblbuff.sys (not sure if it is necessary after installation) Q222902 Ntkern.vxd 4.10.2103 Q224073 Vcache.vxd 4.10.2183 Q230791 1394bus.sys, Ohci1394.sys 4.10.2179 Q243048 Apmbatt.sys 4.10.1999 Q254087 Vmm.vxd 4.10.2000 Q265528 Vnetbios.vxd 4.10.2223 Q282949 Wbemprox.dll (only necessary if WMI 1.5 installed) Q323708 Nscirda.sys 4.10.1999 If anybody has any information, please let me know. Petr

No driver can support ALL usb flash drives and cameras. There are many different chips and protocols used and therefore only limited set of devices can be supported. Maximus Decim pack relies on Windows ME files, i.e. FIVE years old drivers. Windows XP is newer and has better support but backport it to Windows 98 seems to be impossible. Maybe somebody skilled with free time (do you know anybody?) could write the driver, but to test it means tho have several hundreds of different flash disks and cameras - this is impossible for one person, and even for small company. The only way is to use what suits best to you - either Maximus Decim driver, or original manufacturer drivers. Petr

Does anybody know what is the difference between these sets of files: http://support.microsoft.com/kb/192112 File name Version Date Time Size ------------------------------------------------------ Vfwwdm.drv 4.10.2043 8/10/98 9:35pm 15,344 bytes Vfwwdm32.dll 4.10.2043 8/10/98 9:38pm 56,832 bytes Kswdmcap.ax 4.10.2043 8/10/98 9:29pm 51,712 bytes and http://www.visiongs.de/vfwupd.exe that contains: File name Version Date Time Size ------------------------------------------------------ Vfwwdm.drv 4.10.2000 8/21/98 4:56pm 15,600 bytes Vfwwdm32.dll 4.10.2000 8/21/98 5:40pm 57,856 bytes Kswdmcap.ax 4.10.2000 8/21/98 5:26pm 51,712 bytes And now - What are newer? The version 2043 is much newer than 2000, but the date is newer for files from vfwupd. Yes, the date of the file can be changed easily, but even the internal date built-in inside the file in PE header shows August 21st!! And also often newer files are bigger. So - any idea? Petr

Just an idea - what about to add the right link to the registry so that the Windows Update menu item in Internet Explorer will really point to Windows Update site, i.e. http://v4.windowsupdate.microsoft.com/ ? I failed to find the right place just now, probably there are some redirects. BTW, does anybody know any tool that logs http transactions? It would good to see what requests are sent by the Internet Explorer. Maybe it will be different for original IE 5.0 and newer 5.5 and 6.0sp1. Petr

It seems I have discovered the place: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\0 "Icon"="explorer.exe#0100" I was confused by the fact that Tweak UI "Rebuild Icons" does not work for this icon and it is necessary to reboot zto se the effect. Do you know the difference between syntax "explorer.exe#0100" and "Icon"="explorer.exe,0" ? And what does mean negative numbers, like "Icon"="explorer.exe,-103"? Petr

Yes, when I wrote about the HKCU\SOFTWARE\Classes\CLSID\ keys, they were discovered by changing the icons in Display Properties>Effects and searching the registry for updated items. If we want to find an alternative to patching the files, we have to find the right registry patch that will be working in every configuration. I don't know if Gape will like this way, but I think these registry changes could be added to W2kcolor.inf file. Petr

No, at least in RC3 they are installed always, see the RUNPOST.BAT file: if exist %winbootdir%\system\SHELL32.W98 goto sleek start /w rundll32 %winbootdir%\system\ADVPACK.DLL,LaunchINFSection SHELL32.INF,DefaultInstall goto cont :sleek start /w rundll32 %winbootdir%\system\ADVPACK.DLL,LaunchINFSection SLEEK.INF,DefaultInstall REM ----- :cont Petr