Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by sp0iledbrat

  1. You can't have a Class A IP address, a broadcast subnet and a Gateway at the same time? You need to fix the subnet and enter the gateway IP at the least. Or enable DHCP, which the router should support. Cheers
  2. If I had my vote, I'd ask the author not to build it on .NET 4.5 as that would kill the possibility to run it on XP.
  3. "No means No!" only works when girls say it? Gender equality at its finest :g:
  4. If this is the thing, I'm fine with that. I do remember adding ICM profiles for monitor and webcam drivers with nLite and there were never problems. Oh, well, it is what it is. I'm marking it solved.
  5. I noticed (test 38) that when you open WIM manager, you can't select multiple images for deletion (with Ctrl), which is possible in Is that on purpose? I kind of liked that feature...
  6. They may be uncommon, but there is also one for the Dell monitor I'm using at the moment
  7. Well, it says exception code Exception Code e0434f4d can be related to CLR, but afaik, WinToolkit uses .NET Framework 3.5, which is built-in into Windows 7. MSDN forums http://social.msdn.microsoft.com/Forums/en/netfxsetup/thread/87a83f8a-263c-40ff-b768-e371b0a2125e and http://blogs.msdn.com/b/astebner/archive/2007/03/26/how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx say the best way to try and repair .NET Framework 3.5 in Windows 7 is to do sfc /scannow Hope that helps.
  8. All drivers I'm testing with at the moment integrate successfully, apart from this monitor driver for LG 192WS. Is there a reason it won't integrate? I have also attached the driver if necessary. Thank you L192WS.7z
  9. I'm sure it's doable. Both nLite and vLite had that option.
  10. Solved. For those that may stumble upon this: Use Windows 7, since you need to use bcdedit.exe. 1. Run bcdedit /store /enum to get the GUID 2. Run bcdedit /store boot\bcd /delete {GUID} To change the 3 second timeout, run bcdedit /store boot\bcd /timeout 10 Tested and working.
  11. Front, then back: Curiosity. I was born that way. I want to know how things work. Hard truth time: The install worked seamlessly, except for one thing. The option for x64 recovery was still there with the very short (3 seconds) delay, although I used an original boot.wim.
  12. Thanks. I've already seen a few similar guides. At my earliest convenience, I'll test this in the following order: - Use WinToolkit to delete all images except one; - manually replace the boot.wim with an unmodified x86 one; - manually delete "sourc64"; - fire up a VM and then report back. It might just work, but I'm more inclined to expect HUGE errors in setup.
  13. Got it :thumbsup_anim: What about the "sourc64" folder? Is that safe to delete? Also, there is another boot.wim inside.
  14. Say that I have used your wonderful tool to create an AIO Win7SP1 DVD. Now, I just need the Professional x86 version. So, I open Win Toolkit, remove the other versions, make my changes and everything goes fine. During setup, I still get the option "x64 recovery". So, how does one remove it? I suppose it will involve changing boot.wim, but what exactly? Thank you.
  15. It's not even offered on Windows Update in Win7x86, although I downloaded the package from MS Download Center. I'm a bit concerned about the PRE-RELEASE wording. What does that mean? Testing only? Will there be newer, more stable versions? For the time being, I'm not going to install it.
  • Create New...