[the_guy]

@Petr,

that is the batch file I use for the ME SP. It works fine for me.

the_guy

[erpdude8]

the_guy, on Jun 22 2006, 04:23 PM, said:

@Petr,

that is the batch file I use for the ME SP. It works fine for me.

the_guy

thanks Petr & the_guy.

BTW - the_guy, the link to ME Service Pack 2 beta 3 is now dead. Are you almost ready to post up beta 4 of ME SP?

[erpdude8]

Petr, on Jun 26 2005, 12:12 PM, said:

And just to add how it appears to be with the TargetFileVersion directive:
Example is:
TargetFileVersion=#A\IEXPLORE.EXE:4.70.0.1155-:%BrowserWarn%:oK

#A means probably application
#S means system file (located in %windir%\system)
Maybe ther are other possibilities, I don't know.

For version number(s) it the same as for TargetWin9xVersion, but versipn has 4 parts, i.e. it can look like:
TargetFileVersion=#A\APPLICATION.EXE:1.2.3.4-3.4.5.6,5.6.7.8-6.7.8.9:%AppWarning%:oK

I'm still not sure what means the "OK" at the end and what are other possibilities.

BTW, some coder could write very simple tool that would just show the required OS version and FileVersion for given iexpress package.
FileVersions are coded as 4 words (8 bytes total) is the following sequence: For version a.b.c.d the order in the file is b,a,d,c,, no limit = FFFFFFFF
OSVersions are coded as 3 doublewords (12 bytes total) ordered naturally, no limit is FFFFFFFFFFFF.

Petr

and what will happen when %BrowserWarn% or %AppWarning% is used? What kind of message will %BrowserWarn% or %AppWarning% be displayed if you have defined one?

-erpdude

[Petr]

erpdude8, on Jun 28 2006, 07:54 PM, said:

and what will happen when %BrowserWarn% or %AppWarning% is used? What kind of message will %BrowserWarn% or %AppWarning% be displayed if you have defined one?

-erpdude

It will display what you will define.

This is an example taken from some older IE 5.01 update:

TargetWin9xVersion=4.10.1998-:%OSWarn%:OK
TargetNTVersion=0:%OSWarn%:OK
TargetFileVersion=@FileSectionList

[FileSectionList]
1=#S\BROWSEUI.DLL:5.0.3314.2100-5.0.3537.700:%BrowserWarn%:OKCancel
2=#S\INSENG.DLL:5.0.3314.2101-5.0.3533.2600:%BrowserWarn%:OKCancel
3=#S\MSHTML.DLL:5.0.3314.2100-5.0.3541.2700:%BrowserWarn%:OK
4=#S\MSRATING.DLL:5.0.3314.2100-5.0.3539.2200:%BrowserWarn%:OK
5=#S\PNGFILT.DLL:5.0.3314.2100-5.0.3541.2700:%BrowserWarn%:OK
6=#S\SHDOCVW.DLL:5.0.3314.2100-5.0.3537.700:%BrowserWarn%:OK
7=#S\SHLWAPI.DLL:5.0.3314.2100-5.0.3900.7033:%BrowserWarn%:OK
8=#S\URLMON.DLL:5.0.3314.2100-5.0.3537.700:%BrowserWarn%:OK
9=#S\WININET.DLL:5.0.3314.2100-5.0.3539.1800:%BrowserWarn%:OK

[Strings]
OSWarn=The version of Windows you have installed does not match the update you are trying to install.
BrowserWarn=The version of Internet Explorer you have installed does not match the update you are trying to install.

In this example if you will try to install the package on any Windows 9x with lower version number than 4.10.1998 (i.e. Windows 95", you will receive "The version of Windows you have installed does not match the update you are trying to install." error message. If you will try to install this package on a system that contains wrong version of the a.m. files then you will receive "The version of Internet Explorer you have installed does not match the update you are trying to install." error message.

Is this explanation sufficient?

Petr

[MDGx]

I have uploaded the INF + Iexpress guide here:
http://www.mdgx.com/INF_web/
If you prefer to read the INF + IEXPRESS guide offline, download the ZIP, unZIP it + open index.htm in your favorite web browser [HTML Format, 378 KB, English]:
http://www.mdgx.com/...web/INF_WEB.ZIP

Linked from here:
http://www.mdgx.com/add.htm#INF

HTH

[erpdude8]

Petr, on Jun 26 2005, 10:23 AM, said:

Commonly used version ranges by Microsoft:
TargetWin9xVersion=4.0.950-4.0.1212 - Windows 95
TargetWin9xVersion=4.10.1998-4.10.2222 - Windows 98
TargetWin9xVersion=4.90.3000 - Windows ME

the same for TargetNTVersion

Is anybody able to test it?

Petr

I wouldnt use that kind of TargetWin9xVersion setting for Windows 95. That may not work for Win95 B/C systems with the USB Supplement Update installed which updates Win95 OSR2 to either version 4.03.1212 or 4.03.1214.

personally I prefer 'TargetWin9xVersion=4.00.950-4.03.1214' when making patches for Win95

see MS KB article 158238 on the 9x versions of Windows being used:
http://support.microsoft.com/kb/158238

thanks MDGx for posting up the INF + IExpress guide.

This post has been edited by erpdude8: 29 June 2006 - 11:55 AM

[erpdude8]

some of the stuff written in MS article 197147 about Command-line switches for IExpress packages is incorrect. For example the /r:s switch, which supposed to make the package restart the computer without asking the user after install, does NOT really restart the computer automatically. Reading the INF + IExpress web guide about the 'Smart Reboot' switches, it's actually 'AS' [or /r:as]. If you want to force and IExpress package like any Win98 hotfix to automatically restart the computer specify the /r:as switch (or even the /r:is switch if the files that are being updated are in use by the Windows OS).

[erpdude8]

hp38guser, on Jul 13 2005, 11:56 AM, said:

Windows XP SP2 contains already newer Iexpress by default.

Windows Server 2003 SP1 contains even NEWER IExpress.exe file than in XP SP2. WinServ2k3 SP1 has 6.00.3790.1830. Too bad M$ did not include updated makecab.exe and wextract.exe files in Service Pack 1 of Windows Server 2003.

[Petr]

erpdude8, on Jul 24 2006, 05:23 PM, said:

Windows Server 2003 SP1 contains even NEWER IExpress.exe file than in XP SP2. WinServ2k3 SP1 has 6.00.3790.1830. Too bad M$ did not include updated makecab.exe and wextract.exe files in Service Pack 1 of Windows Server 2003.

Windows Server 2003 SP2 (beta) contains even NEWER IExpress.exe - 6.00.3790.2725. Again no updated makecab.exe and wextract.exe files.

Petr

[erpdude8]

Petr, on Jul 24 2006, 11:15 AM, said:

erpdude8, on Jul 24 2006, 05:23 PM, said:

Windows Server 2003 SP1 contains even NEWER IExpress.exe file than in XP SP2. WinServ2k3 SP1 has 6.00.3790.1830. Too bad M$ did not include updated makecab.exe and wextract.exe files in Service Pack 1 of Windows Server 2003.

Windows Server 2003 SP2 (beta) contains even NEWER IExpress.exe - 6.00.3790.2725. Again no updated makecab.exe and wextract.exe files.

Petr

that sucks doesnt it Petr for MS not to include updated makecab.exe and wextract.exe files? I think Win2003 SP2 may come out either late this year or early next year. There will be an XP SP3 sometime in 2007. MS definitely needs to address the date problems when creating CAB or self-extracting CAB files with the Windows Server 2003 version of makecab.exe.

[Petr]

erpdude8, on Jul 24 2006, 10:12 PM, said:

that sucks doesnt it Petr for MS not to include updated makecab.exe and wextract.exe files? I think Win2003 SP2 may come out either late this year or early next year. There will be an XP SP3 sometime in 2007. MS definitely needs to address the date problems when creating CAB or self-extracting CAB files with the Windows Server 2003 version of makecab.exe.

BTW, makecab.exe 6.0.5384.4 (from Windows Vista beta 2) works correctly on Windows XP and uses correctly the "modified" date, not "created" as version 5.1.2600.2180.

Petr

[Camarade_Tux]

@Petr, good news.

Do you know if makecab is now threaded ?
It would be really pleasant.

[erpdude8]

Petr, on Jul 24 2006, 04:03 PM, said:

BTW, makecab.exe 6.0.5384.4 (from Windows Vista beta 2) works correctly on Windows XP and uses correctly the "modified" date, not "created" as version 5.1.2600.2180.

Petr

is wextract.exe also included in Windows Vista?

[Petr]

erpdude8, on Jul 26 2006, 07:26 PM, said:

is wextract.exe also included in Windows Vista?

Yes, it is.

Petr

[erpdude8]

what version of wextract.exe is included in the latest beta of Windows Vista?

[Petr]

erpdude8, on Sep 1 2006, 05:44 PM, said:

what version of wextract.exe is included in the latest beta of Windows Vista?

Vista pre-rc1 build 5552 contains version 6.0.5552.16384

Petr

[Petr]

Petr, on Sep 1 2006, 07:10 PM, said:

erpdude8, on Sep 1 2006, 05:44 PM, said:

what version of wextract.exe is included in the latest beta of Windows Vista?

Vista pre-rc1 build 5552 contains version 6.0.5552.16384

Vista rc1 build 5600 contains version 6.0.5600.16384 (vista_rc1.060829-2230)

I have uploaded iexpress/wextract/makecab/advpack from vista rc1 here: http://home.tiscali....xpress-5600.zip

Petr

[Petr]

erpdude8, on Jun 29 2006, 07:54 PM, said:

Petr, on Jun 26 2005, 10:23 AM, said:

Commonly used version ranges by Microsoft:
TargetWin9xVersion=4.0.950-4.0.1212 - Windows 95
TargetWin9xVersion=4.10.1998-4.10.2222 - Windows 98
TargetWin9xVersion=4.90.3000 - Windows ME

I wouldnt use that kind of TargetWin9xVersion setting for Windows 95. That may not work for Win95 B/C systems with the USB Supplement Update installed which updates Win95 OSR2 to either version 4.03.1212 or 4.03.1214.

personally I prefer 'TargetWin9xVersion=4.00.950-4.03.1214' when making patches for Win95

see MS KB article 158238 on the 9x versions of Windows being used:
http://support.microsoft.com/kb/158238

Versions reported to iexpress package (wextract stub):
Windows 95 retail, OEM and OSR1: 4.00.950
Windows 95 OSR2, OSR2.1 and OSR2.5 without USB supplement: 4.00.1111
Windows 95 OSR2.1 and OSR2.5 with USB supplement: 4.00.1212

So TargetWin9xVersion=4.0.950-4.0.1212 is sufficient to cover all Windows 95 versions and old Microsoft packages contain this range. Newer packages from Microsoft contain wider range 4.00.950-4.03.1214 but this seems to be unnecessary.

MSKB article 158238 does not provide correct information. For example, the version displayed on the System Properties General tab is different:
Windows 95 retail and OEM: 4.00.950
Windows 95 retail with SP1 and OSR1: 4.00.950a (not 4.00.950A)
Windows 95 OSR2 and OSR2.1: 4.00.950 B (not 4.00.950B)
Windows 95 OSR2.5: 4.00.950 C (not 4.00.950C) (after uninstalling USB supplement is changed to 4.00.950 b)

Version stored in registry in HKLM\Software\Microsoft\Windows\CurrentVersion, keys VersionNumber and SubVersionNumber:
Windows 95 retail and OEM: 4.00.950
Windows 95 retail with SP1 and OSR1: 4.00.950a
Windows 95 OSR2 and OSR2.1 without USB supplement: 4.00.1111 B
Windows 95 OSR2.1 with USB supplement: 4.03.1212 B or 4.03.1214 B
Windows 95 OSR2.5 without USB supplement: 4.00.1111 C
Windows 95 OSR2.5 with USB supplement: 4.03.1214 C
Windows 95 OSR2.5 after uninstalling USB supplement: 4.00.1111 b
Note: There are two versions of USB supplement USBSUPP.EXE, 4.03.1212 and 4.03.1214. In all versions of OSR 2.1 and OSR 2.5 seems to be USBSUPP.EXE 4.03.1214 only, KB181661 lists 4.03.1214 version too, USBSUPP.EXE 4.03.1212 I have found here only: http://www.usbman.com/WebDrivers/Win95USB%...ate/usbsupp.zip

DOS command VER reports 4.00.950 for retail/SP1/OEM/OSR1 and 4.00.1111 for OSR2.x.

Windows command WINVER reports just "Windows 95" for all sub-versions.

This post has been edited by Petr: 09 September 2006 - 08:21 AM

[sepehrst]

Hi EveryOne

I have discovered many hidden SED file directives several years ago
I think this is a good place to share it

I suggest you to complete it or provide more descriptions about directives if you know something.

Here it is...


Template.sed

[Version]
;Class=IEXPRESS
;SEDVersion=3
;CDFVersion=3



[Options]
;AppErrorCheck=
;AlwaysPropogateCmdExitCode=
;PropogateCmdExitCode=
;PlatformDir=
;PackagePurpose=InstallApp CreateCab ExtractOnly
;ShowInstallProgramWindow=0
;Quantum=
;CompressionType=NONE QUANTUM MSZIP LZX
;CompressionMemory=15-21
;CompressionLevel=1-7
;MultiInstanceCheck=P or B,"Cookie String" P = Prompt , B = Block
;HideExtractAnimation=0
;UseLongFileName=0
;UpdateAdvDlls=1
;PackageInstallSpace(KB)=
;Compress=OFF
;KeepCabinet=1
;RebootMode=I
;InstallPrompt=%InstallPrompt%
;DisplayLicense=%DisplayLicense%
;FinishMessage=%FinishMessage%
;TargetName=%TargetName%
;FriendlyName=%FriendlyName%
;AppLaunched=%AppLaunched%
;PostInstallCmd=%PostInstallCmd%
;AdminQuietInstCmd=%AdminQuietInstCmd%
;UserQuietInstCmd=%UserQuietInstCmd%
;SourceMediaLabel=
;IEXP_LayoutINF=
;SourceFiles=SourceFiles
;CheckAdminRights=1
;TargetNTVersion=%VersionRange%:%Prompt%:ok OkCancel YesNo
;TargetWin9xVersion=4.10.1998-4.10.2222:%Prompt%:ok OkCancel YesNo
;TargetFileVersion=@FileVersionSection
;InsideCompressed=0
;CAB_FixedSize=0
;CAB_ResvCodeSigning=0,2048,4096,6144
;PackageForX86=
;VersionInfo=VersionSection
;ExtractorStub=


[FileVersionSection]
;1=#S\%File%:%VersionRange%:%Prompt%:ok OkCancel YesNo
;2=#W\
;3=#A\
; #S System Directory
; #W Windows Directory
; #A I guess Application Directory (not sure)


[VersionSection]
;FileDescription=
;CompanyName=
;FileVersion=
;ProductVersion=
;OriginalFilename=
;LegalCopyright=
;ProductName=
;InternalName=
;FromFile= Reads Version info Resouce from Specified PE file


[Strings]
;AdminQuietInstCmd=
;UserQuietInstCmd=
;FILE0=


[SourceFiles]
;SourceFiles0=%Path%
;SourceFiles1=


[SourceFiles0]
;%FILE0%=
;%FILE1%=


;Notes:
;Passing #e and #d parameters to the install command,
;will be converted to <full path> and <directory path>
;of the extractor package respectively.
; It is safer to pass "#e" or "#d" instead of #e or #d

This post has been edited by sepehrst: 25 September 2006 - 04:04 AM

[erpdude8]

MDGx, I have noticed recently that some of the unofficial patches for Win9xME have been created or revised from version 6.00.2800.1168 of wextract.exe. where can this specific version be found?