Well, I just tried converting X17-75238.exe (Pro Plus SP1, verified the hashes that acrsn listed so I believe its a valid file) with version 1.43 and it said "indicated file does not seem to be a supported Office, Visio or Project installer". Am I doing something wrong? Any ideas? Thanks!
Hey Stannieman!!I followed your guide word by word...So I input OFFICE 2010 PRO PLUS (ENG) with SP1 RETAILx86_x64_dvd_730330.iso and checked "Use advanced options". Then, I checked "Add additional files/folders to the installer" and hit the START CHANNEL SWITCHING button.After a couple of minutes, I received the same annoying error message telling me that your tool was not able to create an ISO image. Then an explorer window apperead on the screen, warning me that additional files will be added in the right directory before creating the output iso image.And finally, your tool started building the ISO image...but........guess what?? After more than 3 hours nothing happened yet: is that normal?If so, how long do I have to wait before your tool finally manages to create the ISO image of the VL edition of OFFICE 2010 PRO PLUS (ENG) with SP1 x86 x64 ???
Thanks frjplok, I saw this in Stanniemans release notes: 1.4.1 -> 1.4.2 - Fixed compatibility with .exe installers that have SP1 integrated. But it doesnt seem to be working in this case. Anyway, I can use the CODY tool referred to on the other page you linked to. Thanks!
I have no idea what's wrong with all this, the iso creates fine here with multi arch and single arch installers, and it takes sp1 exes just fine here. The isocreate stuff hasn't changed since a couple of releases ago and there were never problems with it untill now???!
What's in the output install files directory goes into the iso, all the rest is just stuff for conversion, bytes for all editions and channels that need to be changed etc. If you have x64 and x86 you should put all contents of output files in an iso or burn them to dvd. If you only have one of them, only burn/iso all the contents of the desired channel folder. What OS are you guys using btw? Maybe cdimage (used to make iso) has some problems... Links are back online now. I'll send everyone who's having problems with 1.4.3 a new version later today. 1.4.3 was the first to be compiled with visualstudio dev preview on windows 8, I'll recompile on VS 2010 SP1 on Win7. Maybe that's where things went wrong.
Hi Stannieman!! Thank you very much for your reply and above all for spending your time to solve in the attempt this odd issue for free!! I'm using a cracked copy of Wondows 7 Professional turned into a genuine one using Daz Loader, if I'm not wrong....but, since it looks like I'm the only one here having such an issue with your tool, maybe the problem is due to something wrong in my machine or more simply to my bad luck . As for the installer....if I got it right, what I need to burn is only the "Output installation files" folder sitting inside the "Channel Switcher Working Directory" folder, after turning it into an ISO file using IMG Burn, for instance: is that right??
That's right. The contents need to be burned. Not the folder itself! What's your free hdd space? Cause you need a couple of GBs if you have a multiarchitecture iso to convert. For others who have problems with X17-75238.exe, I tested with that one earlier today and it works just fine...
Hey Stannieman, I could not get this to work on XPSP3 but it worked great on my Windows 7 install. So, thanks! Thinking about it, I recently went to Windows update and did the *optional* update to .NET Framework 4.0 ( including security updates that are available for it) on my XPSP3. I am pretty sure that has not been pushed to Windows 7 yet. Maybe that is a place to start - it would not be the first time a newer Framework version broke an app that ran fine on the previous version. Hope that helps somehow!
It doesn't use .net 4. It uses 3.5. As you might know all 3.x frameworks are based on 2.0, so it's all a big extension on 2.0. You can see if you build apps that some framework files are still at version 2.x, even when 3.x is installed. 4.x however is a completely new framework that isn't backwards compatible either, so whatever you do to 4.x shouldn't affect 3.x or 2.x based apps.
Hi I am trying to run this program and I continue to get this error: "The inputed file does not seem to be a a supported office , visio or project installer " I tried this again but now it just stalls its running but nothing happens
I have an odd one. Used the channel switcher and it worked perfectly on the x86/x64 SP1 image from Microsoft. Installed Office on several machines. I have one this morning, though, that I did a clean install of Windows 7 Ultimate and when I run the channel switched Office that worked on other machines, I get the "Enter your product key" screen instead of skipping that and taking me right to the install. Any idea why I'd get this when my channel switched image worked perfectly on other machines?
@Stannieman - I'm currently using your Installer Channel Switcher 1.4.3 version, and I used the River downloads files for x64 & x86 Office 2010 Professional Plus, x64 & x86 Project Professional, x64 & x86 SharePointDesigner, and x64 & x86 Visio. Your program did convert ALL of the files from RETAIL over to VL (except for Visio x86), but for some reason it failed to convert the Visio x86 to VL and never wrote the Visio x86 files to the Output installation files "x86" folder (it did convert the Visio x64, but it seemed to skip the x86 version of the Visio x86 file for some reason). I'm not sure if this is a bug in your program, because I went back and tried it again, and it skipped the Visio x86 file and it never converted the x86 Visio install file into a VL file, and it never copied it to the Output Installation files (under the x86 folder). There is a "Visio.en-us" and "Visio.WW" folders under the x64 folder, but your program didn't convert the x86 file into a VL version and didn't create the "Visio.en-us" and "Visio.WW" folders under the x86 folder. Also the program failed to create the ISO image. (I had to manually go into the "Output Installation Files" folder, and manually burn those files to a DVD. It did create the setup.exe and autorun.inf file, and everything was done correctly except for Visio x86 not being converted to VL and not being put into the x86 folder. Is there any way you can fix this "bug" that is preventing 1.4.3 from converting RETAIL Visio x86 to Visio x86 VL and writing the output to the Output installation files "x86" folder? It seems to work for x64 Visio, but it's not working for x86 Visio.
@Stannieman - I stand corrected. It seems that I simply downloaded the wrong file, and I was actually using the "Project Plus x86" file (instead of the Visio x86 file). I re-downloaded the correct file X16-33056 (instead of X16-32864.exe) , and I'm re-running the program, but I believe I found the problem (I downloaded and used the wrong file for "Visio x86"). Sorry it was my mistake.
Weird... Are you sure you are using the switched version? After the switch all files have the same hash as the original MS VL ones, except for some timestamps the files are identical. I have not the smallest idea about what could be wrong...
@Stannieman - Your switcher works great! Thank-you! Just to let you know, I am running AVG 2012, Avast! 6 (2012), Microsoft Security Essentials 4.0 (2012), Ad-Aware, and Comodo Firewall (2012). The only "issue" was with Comodo Firewall (with "Defense+" activated). All I had to do was just make AutoKMS.exe a "trusted" application, and everything works fine. The AutoKMS works great, and I did check the log (just to make sure that it is in fact updating). It works great, and thank-you!