new version changelog 1.2.5.0:
- Regression fix from path handling improvements. This affected the case when we are copying files that overwrite in the standard architecture directory causing a crash with "Path format not supported".
- Fixed adding updated wmp drivers to driver32.cab instead of driver.cab
- Migrated code to subversion.

Thanks boooggy for the update and sorry about not getting back to you on my prior post. Real life got in the way and no time for browsing the forum

@Boooggy

A “for what its worth” comment. A made a new nlited DVD, with the latest 1.4.5.5?, windows xp pro + sp3 + various add-on’s, component removal, driver integration etc. Everything worked like a charm, however, it turned out that I accidentally deleted the windows media player 11 installer from my hot fixes and also hadn’t installed your slipstreamer. Therefore, when I went to windows updates, I was presented with the option of installing WMP 11. Installed same, and “finally”, getting to the point, I only had to install “one” critical update, the one we have always known, KB941569. So, again, maybe worth noting, no “other” updates seem to be necessary. Maybe it’s a “SP3” thing. I don’t know. Of course, without your slipstreamer, I now have four programs show up in my “add and remove programs” that weren’t there before when using your ‘slipstreamer’. Namely: Microsoft Compression Client Pack 1.0 for Windows XP, Microsoft User-Mode Driver Framework Feature Pack 1.0, Windows Media Format 11 Runtime and Windows Media Player 11. I assume, using your slipstreamer, these are “all” installed they just don’t show up in “Add and Remove” because of the “slipstreaming”.
That’s it. The end.
Hope this helps. Great program, by the way, thanks for everything.
Eddie

yes eddie the wmp 11 installer is made from 4 individual parts. so u will get also the uninstall option for this parts. when u use the slipstreamer those uninstall is not created.
also the hotfixes that appears on my site are also neeeded even if they dont show up on wu/mu

http://www.boooggy.org/slipstreamer/ not working.

EDIT. Now is working, sorry .

Thanks boooggy!

My integration of Windows XP Pro with SP3, IE7, and WMP11 works flawlessly!

hey can anyone help am getting this error

WMP11Slipstreamer v1.2.5.0
Detected source: Windows™ XP Professional SP3

System.ComponentModel.Win32Exception: The system cannot find the file specified
at Epsilon.Win32.Resources.ResourceEditor.ThrowWin32Exception()
at Epsilon.Win32.Resources.ResourceEditor.LoadResourceLibrary()
at WMP11Slipstreamer.CM.GetCabStream(String pathToSfxCab)
at WMP11Slipstreamer.Backend.NativeExtractHotfix(String hotfixInstaller, String destinationPath)
at WMP11Slipstreamer.Backend.ExtractWMP11Installer()
at WMP11Slipstreamer.Backend.SlipstreamWMP11()
at WMP11Slipstreamer.MainForm.WorkerMethod(Object workerParam)

Deleting "H:\WINXPSP2pure\i386\wmp11temp"... Done!

The source being modified has not been damaged.
All changes have been successfully reverted.

please add the full report

What did you choose in the wmp11 installer box ? What is the path to the installer ?

thanks for quick reply

ok am explaining the whole thing that i did


location of WMP11Slipstreamer.exe H:\WMP Spl\WMP11Slipstreamer.exe

path to media player 11 H:\wmp11-windowsxp-x86-enu.exe
path to windows source H:\WINXPSP2pure
after this when i press intergate
it shows

WMP11Slipstreamer v1.2.5.0
Detected source: Windows™ XP Professional SP3

System.ComponentModel.Win32Exception: The system cannot find the file specified
at Epsilon.Win32.Resources.ResourceEditor.ThrowWin32Exception()
at Epsilon.Win32.Resources.ResourceEditor.LoadResourceLibrary()
at WMP11Slipstreamer.CM.GetCabStream(String pathToSfxCab)
at WMP11Slipstreamer.Backend.NativeExtractHotfix(String hotfixInstaller, String destinationPath)
at WMP11Slipstreamer.Backend.ExtractWMP11Installer()
at WMP11Slipstreamer.Backend.SlipstreamWMP11()
at WMP11Slipstreamer.MainForm.WorkerMethod(Object workerParam)

Deleting "H:\WINXPSP2pure\i386\wmp11temp"... Done!

The source being modified has not been damaged.
All changes have been successfully reverted.

am attaching the image to the error please have look to that.
Click to view attachment
Please tell me what mistake am doing

Can you please tell me the md5 of the wmp11 installer that you have ?

If it is not: D1A08DAB82A85BD18CFD54C70EE05671, please upload it somewhere and post a link because I want to look at the wmp installer you are using (it maybe corrupt in such a way that I am not detecting it).

what is md5 & where should i get it in the installer

Download and install Hash Tab 2.0.9.
Then right click on WMP11 installer->Properties->File Hashes

thanks buddy

ok this is what i get in file hashes of my wmp installer

CRC32: A87E8A6A
MD5: 4A3DE150EF717826A3843278509CE7B9
SHA-1: 126607377E36057C0E80CB4C2A2458B6BB6E8678

new version out
changelog here

Looking at the changelog most of it tells me, who isnt a programmer, absolutely nothing.
I've just spent quite some time fixing the files to not install portable devices/drm/network sharing service.
Is there any chance such tweak/removal options will ever be added to this program?

Bonjour a tous et merci pour ce fabuleux petit soft

report bug on v1.3.0.1

"satellite assembly error"
localizer culture mismatch: switching back to default culture

@TranceEnergy: I am working on this (customizations), this should arrive in a 2.0 release, most of the changes are (as you have noticed) not really affecting the resultant wmp11 install, these were cosmetic fixes and localization changes, the INFs were not touched or changed from last version.

@lol69002: I'll post a quick fix for that soon. Stupid mistake from my part (and couldn't test because using english xp with english regional settings)....

That is awesome!!!
I just realized i dont need any of the files in wmp11.cab, so deleted it, stupid thing is i then also have more to update in txtsetup file.
This made my day, i'm getting a beer, wish i could pass one along. Cheers!

thx for this quikly release, 1.3.0.2 works fine

merci

The /output: switch is no longer working in v1.3.0.2 ...

using the /output:"Normal" option returns the below error with the =Value of '0'
using the /output:"Tweaked" option returned the below error with the =Value of '1'

CODE

Unhandled Exception in UI Thread

System.ArgumentOutOfRangeException: Invalid Argument=Value of '0' is not valid for 'SelectedIndex'.
Parameter name: SelectedIndex
  at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
  at WMP11Slipstreamer.MainForm.ProcessParameters(String installer, String winsource, String hotfixes, String output, string customicon, Boolean nocats, Boolean slipstream, String customIconPath)
  at WMP11Slipstreamer.MainForm..ctor(String installer, String winsource, String hotfixes, String output, String customicon, Boolean nocats, Boolean slipstream, Boolean close, String customIconPath)
  at WMP11Slipstreamer.EntryPoint.Main(String[] args)

If I remove the /output switch from my batch, WMP11Slipstreamer opens with all of my settings (with no output type selected), however, I can select the output type and click integrate and the slip finishes.

I have not found any issues with manual Integration.

Issue confirmed, this is due to my localizing efforts moved the code that processes parameters before the code that fills the output type box, leading to this issue.

It will be fixed in next version.

twig
please try new version

Works fantastic, many thanks for all your constant hard work

Works great as usual, thanks!

Is this update also needed ?
KB936782 http://www.microsoft.com/downloads/details...0e-565ea04d1f2b

no
was superseeded by other
and like i said all up2date hotfixes are posted on slippy site

new version out
1.3.2.0
please check the site and forum.

Hi Boooggy,

I did an nLite (v1.4.7)+Slipstreamer (v1.3.2.0) integration for a WinXPx64 installation running on a WinXPx64 OS. Everything was perfect, better than ever before .

Howerever there was one small error left: after installation the log showed a registration error for qasf.dll.
-I found this was caused by the 32 bit version of qasf.dll being present in the system32 as well as the sysWOW64 folder.
-I fixed it by copying the x64 version of QASF.DL_ back into AMD64. Official MS installations do not show this problem.

Please look into this

thx for reportin dutchman
we will investigate and see whats up.

Your WMP11 slipstream website lists the hotifx KB941569 which comes as part of a
hotfix. Although the link below says it's for SP3 too, the actual download page for this
KB# only shows it as SP2 for OS' it applies to; moreover, the date on the download page
shows a date of 12/10/2007. Am I safe to assume that it was included in SP3 now since this
fix was in FY' 2007? Thus, is this hotfix obsolete now for WMP11 due to SP3 coming out which
means this KB # would need to be removed from your website?

http://www.microsoft.com/technet/security/...n/ms07-068.mspx


Also the verions of the wmp11 slipstreamer shows v1.3.2.0. But if I select the slipstreamer link below
it, the file name contains 1.3i. and not the version number mentioned. Am I selecting the right file for
wmp11 slipstreaming or should the filename be corrected to the correct version?

KB941569 contains wmp 11 related file so sp3 doesnt update that .......so this fix is not obsolete.

the installer shows version 1.3.2.0 if u keep your cursor over it.
also u can check the md5 hash.

these 2 hotfixes are not listed but once were can I ask why they removed from list?

they both not superceded

KB944110
and
KB942264

Microsoft usually does not list when a hotfix supersedes another hotfix. (They do this for security updates, but not for hotfixes, especially those that are not core Windows components, like WMP.) So when it comes to hotfixes, you must extract the packages, look at the payloads, and then compare the file versions of all the modules the collective group of hotfixes replaces. If you do that for all of the hotfixes on the current list, plus the two that you have inquired about, you will note the following modules and file versions:



So KB945381 rendered KB942264 obsolete, and KB950478 rendered KB944110 obsolete.

NOTE: Some hotfixes replace two or more files, and another, more recent hotfix may only replace one of those two files. In such a scenario, you would still require both hotfixes.

ok got it thanks.

dutchman
i looked into this issue and found out that slipstreamer works just fine with wmp 11 x64 and hotfixes.
the issue u had is cause u integrated kb939209 via nlite and not with slipstreamer. as far as i see nlite overwrites qasf.dll x64 version with x32 version.
thx for reporting
i will get in touch with nuhi to solve this problem.

Wmp11 streamer v1.3.2.0 crashes on win 2K SP4 with all the latest patches and it also has dotnet 1.1 plus the hotifx and
dotnet 2.0SP1 (which includes 2.0 and the sp1 combined). I have no problem running the latest Nlite which needs dotnet 2.0+.

I use the vanilla setting, and dont select the either of the two checkboxes.
The only data fields I enter are the selections for the "wmp11 media player" software, the winxp pro sp3 directory and the
wmp11 patch diretory that contains the list of patches from your website.

The error I get is a popup window title "windows - no disk" with the following exception c0000013 and the parameter
7cc31d6c repeated four time across the screen.
Note: this is not the c0000135 error listed in the FAQ section.
Note2: I do have an IDE ATAPI type Iomega 250meg zip drive installed with no disk in it; however, I'm only specifying
a hard drive partition on a 750 gig seagate drive whereby the partition I'm using is 323 gigs and not the zip.

Here are the steps to reproduce the problem.
a). I specified and selcted for the first field the directory where the wmp11 media player software is located.
as, H:\wmp11\wmp11-windowsxp-x86-enu.exe
b ). I then selected the second directory and when the popup box is shown to select the drive and directory where the
windows xp source to be integrated is at, the "windows - no disk" with exception is shown. Of course, if I keep selecting
the "cancel" button, the error will go away after about 3-5 times of trying to "canceL" and then I can select the location of
the windows xp source as, H:\VRMPVOL_EN\I386 . However, once the line is filled in, it is highlighted in a light reddish color.
c). I can then select the third text box to specify where the wmp11 media player patches are at as,
H:\wmp11_fixes\..... note: ... . is the list of files I selected that are the ones you specified.

d). Upon doing items a-c, the "integrate" button remains greyed out. I then just exit the program.


The 2nd variation that generates the exception above is done similarily by doing the following.
1). peform step © from above first.
2). perform step ( b ) from above second. The exception is generated and keep hitting cancel. The field is also then highlighted as light colored red.
3). perform step (a) from above third.
4). The "integrate" button still remains greyed out.

The 3rd variation that doesn't generate the exception but doesn't work either is as follows.
1). peform step ( b ) from above first. Thus when I specify the windows xp source's I386 directory the text box is still higlighted in a light red color,
and no exception is generated.
2). peform step © from above as second. Note: I could've also done step(a) from above too instead of step ©.
3) peform step (a) from above as third. Note: I could've also done step © from above too instead of step (a).
4). The "integrate" in this case still remains greyed out.


Conclusion:
In doing any of the above three possible ways/combinations/variations of selecting the directory and then trying to do an 'integrate"
the slip streamer doesn't work.

Ok let me clarify the problem:

1. The light red color is because the folder you selected is the I386 folder itself, wmp11slipstreamer is looking for its parent folder, in your case you need to select: (H:\VRMPVOL_EN), this will make the light red colour go away and it will also re-enable the integrate button (it gets disabled when prerequisites are not satisfied).

2. The "windows - no disk" is happening because Windows is trying to access your ZIP drive for some reason. When you choose a drive and press OK or type manually into the box, I try to access the path to see if it has an I386 folder, but it shouldn't do this in the Select folder dialog unless you specifically mouse over it or some buggy AV is trying to overzealously scan the drive (and still thinks it has media in it).

In any case, I am not doing anything besides calling the standard Windows functions to display that dialog in my program, I don't know why its happening to you and I don't have a ZIP drive to try.

But in any case, if you look at point number 1, you will be able to get past the issue and continue.

new version out
changelog
http://www.boooggy.org/forum/viewtopic.php?f=12&t=14

about (1). But doesn't it say in the text above the box that contains the directory to the OS source to make sure to include I386?
OK, I interpreted the "(must contain a "i386" folder)" to mean, that I had to include the I386 in the WIN OS directory path. The
correct meaning is that the Windows OS source tree had to have an I386 folder in the directory tree.
about (2), In all my cases, I hit the button on the side that causes the popup box and displays the list of drives to select where the OS is at.
Thus, when you call the MSoft standard functions, is it possible that they internally scan for all drives on ones PC before displaying
a list of drives to select. Hence, when they get to the ZIP drive an exception will be generated like I'm getting.
Note: This exception is the same problem I'm having when IOBIT Defrag scans for drives, display a list for one to select for defragging.
In this case, an exception is generated since my zip drive doesn't have a disk.

Software Suggestion: When MSoft windows functions are called to scan for a drive list and an exception is generated, couldn't your
software handle/trap on this exception, and then just ignore it? Thus, the drive causing the problem is ignored
with the rest being displayed? In the case of an exception being generated for every drive should the drive
(if there is only one in the computer) or drives be bad or don't exist, the exception(s) would be grouped
together and it is at this point a popup box would display , not an exception, but a friendly message saying
"NO drives found".

In the end, all software "exceptions" will be handled for gracefully.....

Question: Do you you have a list of the exception codes and their return values that you could post or reference here?
The reason I ask, is that besides WMP11 Slip streamer and IOBIT Defrag, Acronis Trueimage and Echo have this problem
due to my zip drive not having a disk inserted in it. WMP11 Slip Streamer and IOBIT generate annoying popup box exceptions,
whereas Acronis Trueimage and Echo on startup,, scan the drives and write a Bad disk block error to the application event log.
They've had this since v8 and haven't fixed it either.

Here is MSoft's response to an email that I sent them. They will update the KB article and download page for Windows XP SP2 to include
in the Supported OS section, the addition of SP3, so that it is clear that this patch applies to both SP2 and SP3. The actual security pg
did specify for WmP 11 that it was for SP2 and SP3.

Unfortunately this error is not generated by WMP11Slipstreamer, it is generated by Windows itself outside of my control, so I can't do anything about it unfortunately (and so can't most apps that scan all drives).

Meanwhile apps that do trap this error don't try to display that dialog box (Windows scans the drives by itself when you open the dialog box outside of the calling app's control). So I cannot fix this.

This is an issue also with old style floppy drives and legacy removable drives.

I have a floppy drive in the computer too with no disk inserted.

If all removable drives such as floppies, zips and powered down drives (i.e a spare swap drive in raid)
have this problem, I wonder why CD/DVD drives without a disk inserted aren't generating exceptions
but seemed to be ignored when they display the list of drives to select from in the dialog box?
Is Msofts software smart enough to ignore these as special cases?

Because optical drives (CD / DVD) communicate using a special command set (the ATAPI inteface) over the IDE / SATA bus and there is a way for the optical drive's firmware to notify the operating system when there is inserted media or not.

But old drives that communicate via fdd interface don't work properly with this design because they have no way of notifying the operating system, instead they depend upon checking to see if there is media or not by trying to access drive directly (also there is supposed to be mechnical way of detecting thise case IIRC) and then Windows is supposed to consider the drive failing to read as no media detected...

Sometimes this doesn't work, so you see this exception, MS doesn't try to fix because floppy drives / ZIP drives today are a thing of the past.

What about a Windows Media Player v9.x slipstreamer for those of us that have Win 2K Pro
and not XP? Is it hard to modify WMP11 slip tool so that it can slip 9.x into the Win2K OS because
WMP10 and WMP11 will not install under Win2K? One could just slip WMP9 or WMP10 only into
the XP os if one doesn't like WMP11. Thus, could WMP11 be modified to do either Win2K or XP
for these older WMPlayers?

BTW, after removing I386 from my directory path and ignoring the exceptions by hitting cancel,
I was able to slip WMP11 into Win XP Pro SP3 without any problem on a running WIn 2K Pro machine.
I haven't tried installing this slipped XP Pro SP3 with WMP11 on a spare machine yet.

new version 1.3.4.1
changelog
http://www.boooggy.org/forum/viewtopic.php?f=12&t=14

new version 1.3.4.2
changelog
http://www.boooggy.org/forum/viewtopic.php?f=12&t=14

Thanks n7Epsilon, I've played around this weekend on it.

I booted into safe mode and no exceptions get generated for any software including iobit defrag which I can run
in safe mode without any problem. I wonder what safe mode does differently vs. running windows normally?

http://www.consumingexperience.com/2007/11...processing.html
http://forums.cpututorials.com/viewtopic.p...&view=print
http://support.microsoft.com/default.aspx?...kb;en-us;330137


There seems to be two different types of exceptions for No Disk generated. With other slight variations on the numbers.


Per a post on a RU site....



per consumerexperience site....



I changed my drive letters around and it didn't fix the problem.

Most of the internet posts point to uninstalling any hardware that has a removable media. CD/DVD, floppy, USB, Zip etc.
Also it can occur during startup (startup programs), uninstalling apps or installing them i.e. virus checkers, MSoft s/w products,
third party software, freeware, and MSoft updates - just about anything from the posts I've seen on the net. Some people uninstall
and reinstall, some just disable the software i.e. startup, some just delete the software altogether, some just uninstall/reinstall all the removable
media drivers, some remove the icon for the s/w in the systray, etc until something works.

Make the annoying error message disappear based on a MVP article. See KB281345 and it does mention Zip drives too. Registry fix.
http://pubs.logicalexpressions.com/Pub0009...icle.asp?ID=593


Presently, this is what I have to do to get IOBIT defrag v5.0.1 not to complain since nothing worked except put a disk in the Zip drive all the time.
I do have a newer quicktime installed which some say causes problems. I could uninstall it and see if IOBIT starts working. See info below.
Using Windows Defrag doesn't cause errors. Here's a post about JKDefrag doing it. http://www.kessels.com/forum/index.php?topic=904.0
On Oracles webite a post: http://forums.oracle.com/forums/thread.jsp...2&tstart=-1




Ultimate fix is to put floppies disks or zip disks in the drive all the time if all else fails or do the KB281345 registry fix way.

The solution to WMP11 all versions is to uninstall the floppy, zip and cd/dvd drivers then reboot and let windows detect the hardware and
reinstall the drivers. After doing this wmp11 slipper didn't complain anymore.

Now onto why IOBITDefrag complains....

I had similar issues and some succes with setting:

HKLM\SYSTEM\CurrentControlSet\Control\Windows ErrorMode 2

This redirects error messages to the event queue and does not pause execution.

The default ErrorMode value is 0 and it is best that is stays there. The above tweak is a last resort.