Jump to content

RicaNeaga

Members
  • Posts

    845
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by RicaNeaga

  1. Ok... then another idea. How about making the tool smaller in height by making the win toolkit guides button from main as another row in the welcome tab, below getting started? You'll then have 4 buttons in the main tab, 4 in the intermediate, and two in advanced, making the advanced tab not seem so empty as it is now. Also, by making it smaller in height, the usused space in the left column, below Repot Bug and WPIW, would also be smaller and probably also make it look better overall. Once again, just a thought.
  2. Those lines are very transparent, and if the desktop wallpaper is very dark, the same are those lines. And yes, the issue is gone if I untick the 'Tools Manager Aero' option. So maybe you can set thyose lines with a lower transparency by default. The overall design I think it's a stept ahead over the old design. So congrats, I like it very much! :dancing: Besides that line, that's very annoying, only one suggestion: maybe it would be better to move the All-In-one Disk Creator from the Intermediate tab to the Advanced tab, for two reasons - first, a better look, the advanced tab seems rather empty with only two buttons, second - the many issues (I've seen them here in the forums, I've never created such an AIO disk) that arise by modifying such a AIO disk. So maybe moving it to the Advanced tab would discourage new users to make them.
  3. I don't have good news Same error with the WU update (windows xp x86 sp3), about a service not working (BITS, Automatic Updates or Event Log - not the case, weird error). Some observations though: - when I arrived at update.microsoft.com, it made me update windows agent. I couldn't see what was really installed, because the installed update tab was unaccesible (again, the error) - I'm clueless, but I don't think it could have been .257. However, when I installed your AIO with .257, it didn't make me install anything it went straight to giving me the error, so maybe .257 it's seen / named by Microsoft (the same) as .256; - went to microsoft update, again installed the microsoft update client via the browser (IE8), and again the error; I'm as I've said clueless, and I can only help you by testing another version again. But please look more into this, since I can confirm there's a 100% working solution with the web WU/MU (xable's older .226 addons) and I really think the error is replicable on the majority of systems out there.
  4. Tried both this one (the ryanvm aio installer) and Onepiece's true addon, also tried the previous version from Onepiece again, and I found out that what a friend of mine discovered is true - the online microsoft.com or windows.com update sites won't work with it, gives a strage error like the BITS service isn't working. It also doesn't work with BITS started and also set to automatic. I wasn't able to detect this error before because I didn't update through IE, I waited for the updates to appear in the right corner of the taskbar. And I'm pretty sure you can duplicate this issue on your live system. I however found out a working solution - 7.4.7600.226 ''latest'' official xp version works with IE updates. Actually I went back to xable's addons. So just a thought - maybe you'll consider at some point also making a 7.4.7600.226 version for xp users. Important update: I forgot that when I first went to update.microsoft.com site, a pop-up window appeared, and made me install something - it was Windows Update Agent 7.6.7600.256. Although it's not beeing pushed through WU, it's the latest ''official'' version. This doesn't change the fact that I can't use IE to update (the usual method is ok, updates do appear in the right corner of the taskbar both with your pack and with Onepiece's), unless I use xable's 7.4.7600.226 packs (WU+MU) and then I update it to the latest version through Microsoft's servers.
  5. Tested it twice on a live system, with two nlite runs (and a third one that revealed nlite limitations), just to be sure. So yes. it really works, and WU is ok, however you MUST name it rootsupd.exe, otherwise nlite won't work with it. Thank you very much for the help.
  6. I have a problem with this one, both the modified and the official version, so it's not your fault. The problem is that although it gives an error if I try to add it as a normal update in nlite (rootsupd.exe is ok added directly in nlite), it gives the same error when I try it as an addon, during T-13 (rootsupd.exe is again ok). And it's not a problem of the order of installation, as rootsupd is surely beeing installed first. So do you think you can modify this installer somehow to correct Microsoft's flaw, making it addable to an offline image, or is it usable only on a live system? Thanks. LE: Or can you make an AIO installer with both, that also satisfies WU?
  7. Ok. Long story: nLite was developed by a prodigy nick-named nuhi. He was later hired by Microsoft. When xp was around, and later when vista came out, administrators had come very nasty tools (very hard to use - way too much knowledge involved) called WAIK. vlite for example needs WAIK (or a slimmer version Kels uploaded here I think, I don't have the link anymore - I gave up vista ~a year ago after making me go nuts ). Later came RT7Lite that also involves the WAIK way of configuring your install. nlite besides beeing easy to use, and making ''kids'' everywhere become ''doctors'' in windows installation, had some breakthrough features like beeing ~ idiot-proof when it comes to removing stuff from windows or the first real AIO tool of its kind. Later however, don't know if nuhi had anything to do with it or not, beeing a Microsoft employee then, when Windows 7 came out, it had DISM integrated in it, a tool maybe not so versatile as WAIK, but more elegant and easier to use. Most features from AIO of Win Toolkit are just calling DISM from your OS to do the stuff you tell it to. DISM also has a remove features option, really not so ''evolved'' as in the WAIK for 7 version, and not so obvious in size-shrinking as that. Lego promised that in the future will bring some advanced vlite-like features of removing stuff not available through DISM, but you'll have to wait for them. You have one however right now, that really makes a difference when it comes to size shrinking, and its related to the natural language in 7. So please be patient for other removing features. However, if you think that the current ones are buggy, enumerate them (so it makes the job of Lego easier, since you have a tendency of posting long stories like this one).
  8. If files aren't deleted from the iso I think you shouldn't worry. However, what is the end result after you install it on a live system? Are the stuff still there? BTW, making xp slimmer with nlite has nothing to do with making 7 slimmer via DISM, the differences are many and I'm sure you're aware of them
  9. compstuff, so this is only a cosmetic issue, as it ONLY doesn't show in the integrated tab, or can you confirm that v32 has issues with INTEGRATING those WU cabs via AIO (DISM)? I'll try it later but I'm not in the mood for experiments, I just want to get the whole process completed without glitches.
  10. If you have time Lego, it will be great if you could also make those .cab (names) go green instead of red, since DISM integrates them perfectly. You can find them here (x64) and here (x86). Thanks
  11. Since the above problem is solved, I add a minor one (I don't line starting threads many ) from the latest build: The driver uninstaller pops-up a ''Stop!'' windows after every driver uninstall, with only ok as the only option. Everything runs smoothly, the driver is rerally uninstalled, so it's really only a cosmetic problem - for 10 drivers I have to press that useless ok button 10 times
  12. Interesting installer - thank for your work. Two questions though: 1. Is the x86 installer usable with windows xp at T-13? Probably I want to make an addon out of it... 2. Can this installer be used alongside with Onepiece's Microsoft Update 7.4.7600.226 true addon? The reson I ask is that I'll also want the office updates to be ''activated'' by default.
  13. I remember I asked in the past for a previous build Lego to make those cabs turn green since DISM integrates them. However, now they're updated, so... LE: Actually, komm uses a different file name for those files. I'm pretty sure if you rename them so they'll match the name of the cabs from SoLoR's repository they'll turn green |WinToolkit is already modified for those names...
  14. Then please add also support in your next versions for KB917607, KB943790 and KB971033. These are add-on functionalities to windows, and they're installable to an offline image, so the bar shouldn't be red, but green in WinToolkit. Thanks
  15. Lego's implementation of this feature is very good, I've seen many updates that weren't supposed to be integrated going red. Also have some ''add-on'' to functionalities in windows that go red when integrating through DISM, so I integrate them online, through silent installer's RunOnce at first logon. That's my suggestion for this one also
  16. After trying three silent switches that didn't work with WinToolkit's Runonce, I can say for sure that /quiet /norestart works with this one. Actually the only working switch with WinToolkit's Runonce
  17. Just wanted to say that everything is ''as advertised'' in version 23 No more silent installer or msu problems. Congrats Lego!
  18. Thank you very much for solving my request, however please update the explanation for the /ai switch with smth like ''only C++ and extra VB/C are installed''. From your current explanation some may understand that the extra (old) VC are skipped
  19. The tweak regarding metro, Lego. From the rumors, although it works now, it won't for the final version of win 8. But there is no reason to remove it now however, I was mistaken
  20. I've never had such problems, even with the latest build v20. I've tried to find them in repo from here, but they're not, not even one. You should delete them ALL and recheck you updates with the ones from that link. btw, once again great job Lego with this feature. As I can see now not just for ''show'', really useful.
  21. I was reffering to .msu updates NOT through DISM (works very well since the beginning of time), but as silent installers. The safe bet is still version 10, I'm pretty sure in v18 .msu will not be installed when run at first logon.
  22. From what I remember version 18 had different issues (like .msu not installing), so make all the changes with build 20, except silent installers & not-integrable-to-an offline image-.msus with build 10 from here. But I'm hoping since Lego is back to solve this frustrating bug once and for all.
  23. I'll start with the official link - here. Hopefully I'll come back later with direct-to-Microsoft-servers links, as computerbase.de already has access to such direct links for the german versions. Enjoy it if you can... Nevermind my previous post, you can get the english ISOs from here (Microsoft servers). Also the ISOs for other languages are posted below. EDIT: Apparently Microsoft say you need a serial key, and they recommend everyone to use: TK8TP-9JN6P-7X7WW-RFFTV-B7QPF
  24. Got it from here (that has this article as a source). Made it into a thread because of its significance for power users. Seems like the days when a few (idiotic) people from Microsoft are behind key-decision-making are sadly back. A move like this also is making me remember of the vista days, when end-users were the least worry Microsoft had, and bloatware features were embelmatic for their thinking. We'll find out tommorow, from early-reviewers, as the rc will be live today. LE: You can remove that tweak for windows 8 from WinToolkit now, Lego
×
×
  • Create New...