Jump to content

Mr_Smartepants

Members
  • Posts

    807
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by Mr_Smartepants

  1. That's great. I wasn't aware of your workaround. Sounds like a smart move. Looking forward to your latest fixed beta to play with.
  2. You might want to rethink that option. The latest RVM Integrator has the WBEM fix integrated as well. I think Nuhi is fixing nLite as well. Or at least make the WBEM fix an option.
  3. Getting this same error with 1.0.10.9. I'm using XP Pro VLK SP3 MSDN. Here's the first 8 lines from EULA.txt I assume you're script is searching for the string 'MICROSOFT WINDOWS XP PROFESSIONAL EDITION' in which case mine is on the 4th line.
  4. Looks nice! Download link gives error 404 though.
  5. Funniest thing I've seen all day!
  6. Throw in an empty HDD and give it a whirl! If it doesn't work, you haven't lost anything. Although I would avoid XP-64 like the plague though. Driver issues mainly. Vista-64 is pretty solid. I've been using it for months.
  7. Yeah, I was going to ask about the grey background behind the text. I also have another bug-report. Integrated 1.0.10b7 into XP Pro SP3. After install on real hardware, Boot screen not modified. Standard XP flag-type bootscreen. Install same ISO under VirtualBox works fine. Weird.
  8. I just patched my XP Pro source with XPtsp.v1.0.10b7 and WOW! That looks the best ever! The IE download image was centered, all the animations worked. Simply marvelous! Keep up the good work guys.
  9. That's a nice score for a notebook. My buddy's MacBookPro gets 4.9 running Vista. Sadly my 3-yr old Gateway notebook only gets a 3.0. (XP was promptly reinstalled!)
  10. Detected OEM Home just fine! Yeah, the OOBE 'follow-on' Home graphic doesn't look all that nice. The 'Home' text and Windows flag are stretched vertically on 1024x768 screen and the resolution is poor. But the detection script worked! :thumbsup_anim: I saw this too. Offset too far to right.
  11. I have OEM Home, I'll give it a shot and report back tomorrow.
  12. Exactly what errors are you seeing Kel? The only error I consistently get with some addons in RVMI is "No entries*.ini found, exiting".
  13. Well, I uninstalled nlite then reinstalled clean. Still has the .iso boot issue. This isn't a problem with XPtsp, it's a nlite problem.
  14. Q6600 Quad-core running Vista x64. And I don't have a problem building the .iso. If I build it in nlite, then the .iso won't run under VirtualBox.
  15. Yes, that's exactly the same error I get in VirtualBox. The program just resets over and over. You don't even get past the "press any key to boot from CD", once you press a key, VirtualBox resets again. I just figured it was nlite was broken and used RVMI instead.
  16. I also can't run an .ISO built with nlite 1.4.8, but using RVMI to build the .ISO works great. Isn't it then an nlite problem?
  17. Siginet wrote an autoit script that does that already. It's part of his oemscan addon. http://siginetsoftware.com/forum/showthread.php?t=276 If you ask nicely, I'm sure he'd share some of his code with you.
  18. No problem. An automatic .bat is really the way to go if you can pull it off.
  19. It might be as simple as adding the code to the beginning of the .bat: @ECHO OFF ECHO 1. Windows XP Professional ECHO 2. Windows XP Home ECHO 3. Windows XP Media Center Edition set choice= set /p choice=Please choose the Windows XP source version you are patching: IF '%choice%' == '3' GOTO MCE IF '%choice%' == '2' GOTO HOME IF '%choice%' == '1' GOTO PRO :PRO ; do your file copy thing here GOTO check :HOME ; do your file copy thing here GOTO check :MCE ; do your file copy thing here GOTO check But it's your code, and ultimately your choice. Whatever is easiest for you. We all have lives outside these forums.
  20. This only refers to the addon. The standalone installer does not require RVMI or Nlite, and will patch your source without issue. http://www.wincert.net/forum/index.php?showtopic=3842
×
×
  • Create New...