Hlafordlaes

@OP, The target market for this type of tool is relatively small. Most use it for rolling their own local install, I'd venture to guess. The AIO and x86/x64 combos (pardon my layman terms) should be reserved for a Pro version, as these would presumably be folks looking to do multiple installs, giving them a reason to invest. I'd say up to some €50 for a corp or site license would be OK. (I wonder, though, if there is much room between hobbyists/power users and corp users of Windows IT tools.) A Win10 version should offer an upgrade at a lower price for 8.1 buyers, and be free for those who bought it in the last 6 months. My $0.02... and thanks so much for the tool.

Even though I am in Spain, I use the English version software. (Como soy un expatriado, pu

Thanks for that, Ricktendo. In my own attempts I had identified all of those, plus awaymode160.cat in the svcpack folder, but I thought if I left devcon it would be OK (isn't devcon just the cmd line equivalent of device mgr?). However, and the reason for my post, is a small issue: I do not see an autorun.inf in the unpacked addon nor a reference in the entries file. Isn't that a typo? Can't speak to the MCE-specific integration results yet. My modded and repacked addon hasn't been working for me, but every indication is that there is a problem with some other stuff I am adding. Should know soon enough. One issue for me has been to maintain a stellar .Net1.0 install (apparently important for MCE or TabletPC), get .Net1.1 installed at T-13 for this addon, and still add .Net2.0-3.5. Latest test shows that a hand-rolled .Net1.0SP3 plus the DotNetFx_All_In_1_Addon_v2.3.7z from RyanVM.net, installed in order at T-13, all show up fine in my VM tests. Using Aaron Stebner's .Net Verifier tool, one still gets missing file error flags for 3.0 and a couple of other SPs, since the XamlViewer files that 3.0 adds are uninstalled by later fixes or 3.5, don't remember which. I extracted these files from 3.0: XamlViewer_v0300.exe.manifest XamlViewer_v0300.xbap XamlViewer_v0300.exe and stuck them in $OEM$\$$\Microsoft.NET\Framework\v3.0\WPF just to see if that was the only issue. Sure enough, with that "cheat" the Verifier reports 100% OK on all frameworks after a fresh install (I am keeping the files there; hope that doesn't bite me later).

Away Mode Woes I tested and retested my integration with this Addon in MS VM until everything was flawless. Burned to DVD, installed, and... panic time!! The MS doc on Away Mode states that only computers with a compatible BIOS can use it, and warns that many systems may not be, which is why the functionality was not released to the gen public as an addon or update. Guess I'm one of the unlucky ones, which is why I am posting in case this happens to anyone else. Symptom: The Away Mode device appeared in Device Mgr (OK), but no matter what I did with chipset etc drivers, my system could not detect my SATA DVD burner, and Explorer was showing some of the OS protected files with that option turned off in Folder Options. Scary! Solution: Unfortunately, without access to the burner, there was no way to adjust anything and do another burn. Had to quicky re-install my previous slipstream to avoid any possible disc corruption and to be able to take another crack at slipstreaming. Aaarghh. Now going thru the addon to check for all the .cat, .cabs and what-not to see if I can't get a successful install...

Ahhhh.... Now I can stop kicking the dog. We both thank you! O sea, muy agradecidos los dos. Edit: didn't want to repeat the image, nixed it.

I realize this is a non-issue from anything but the purist, dogged-perfectionist mindset... which many end users making slipstreamed installs seem to have. I do, lor help me :-) (After all, in the age of DSL high speed downloads, the slipstreaming effort, at least with respect to Windows Update, is hardly as worthwhile as when we were all having modem drop-outs after a Win98SE install and wishing for a local, up-to-date source.) But I seem to be a niggler and cannot resist trying to get my slipstream to be rabidly up to date, including downloading any WU hotfixes detected when testing my integration in a VM and manually adding them to my svcpack. So, thought I might obsessively ask: How did Orbit_30 get his addon to show 2005? Is there a dll hexedit hack or something I might try to reproduce that magic 2005 number? (Heard of the registry edit to ver4.0, but that does nothing seemingly.) Or is this "As Good As It Gets" for us O-C sickoes? Edit: spelling

Thanks much for this, sir. I use many of your RyanVM addons for my XP slipstreaming, which have always worked just fine, as well as WPI. I keep a "classic" PC around for Win98/DOS gaming, and am due soon for a re-install and update; this tool will really help. Kelsenellenelvian has become a "trusted brand" in our household. Thanks ever so much.