When extracting an ISO of an office installation using the customize setup tool, all the files have a single letter extension. Is this a bug or by design?
Actually, it looks like it's the extension minus the final 2 letters. This happened when I extracted WZOR x86 select edition but also when I used it on a Standard Retail ISO
Confirmed it myself, not sure where it came from but this is noted. For now, extract the ISO through other means like 7Zip, and convert/do stuff, and if you want a new ISO, try building that, and if the issue occurs when making an iso, use a different ISO builder. Think I found the problem. It's a quick fix so I'll probably update today.
V2.1.2 released and fixes ISO extract. The problem is because some ISO's I extract added ;1 to the end of the filename, so I subtracted 2 from the filename, but this screws up ISO's that don't add that to the filename (it has to do with the ISO library I use and type of ISO), so now I check if the ;1 is there and only remove 2 from filename if the ;1 is there.
@CODYQX4 Thanks. Backup now working. But, what have you done? Since I don't see backup fix in the changelog.
I didn't change anything for Backup. I just fixed an ISO bug. I said the backup issue might have been due to registry issues and following some of my suggestions may have fixed it. That or it was a rare issue where a file doesn't write in time.
Microsoft Office Professional Plus PT-BR x86 Trial, asks for the serial on installation, downloaded from M$.
SFX EXE, ISO, or extracted? (I can't seem to find a link to that version direct). PS: If it is extracted already you have to press Installer Path, not Extract Setup. The exception is being thrown for whatever reason because after detection, no entries are added to the comboboxes.
Can you extract it and show me a list of files/folders? As I said that exception is being thrown because for some reason the dialog boxes detected nothing. This could have happened by language or office sku, or something screwed up in extraction. And this is Pro Plus, not Pro right? Because if you have a SingleImage.WW folder, that installer is not supported.
OK that is not extracted in the way I meant but good enough. Delete that folder, and hit extract setup (not installer path) and select the DL'd EXE file that when you run it.
@Bosh if you are going to do UI work, just use the last version of the source you have. My FTP host is dead right now, and the code in question hasn't changed very much (except for 2.1.2 where I made a minor change). The current code is a bit current UI dependent. I can fix up the code to accomodate the UI changed @Anyone else Please give suggestions to help improve the Customize Setup Tab UI. I made that UI myself during the long pre-beta work for V2.1 and it hasn't really been thought about too much as other things have taken priority. We need these suggestions to help with the UI improvements as I myself can't really think of a way to improve it (That's why first order of business when we started V2.0 was for Bosh to make a UI, I'm better at back-end code than nice UI's).