Ruu

Member
  • Content count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Ruu

  1. Thanks for the update, jvidal!
  2. Hell Racer, can you re-upload your lite version of XPize? I'm rather late to the party and the links have all expired. >.<
  3. tommyp, thanks for your pointers. My problem was indeed a very simple and embarrassing directory naming issue, not noticed until a proper night's rest, lol. All seems fine now! Thanks again.
  4. I have run this three times to make sure I didn't do something wrong, but it seems that the latest HFSLIP beta (1.7.10 J) completely stops processing after extracting the HFs. I see a SOURCESS folder, a WORK folder, and a TEMP folder when it starts running. After HFSLIP goes and extracts what looks like all of the HFs, the TEMP folder disappears, leaving me with just a WORK folder and a SOURCESS folder. The WORK folder is 198 MB and the SOURCESS folder is 4.55 MB. There is no log. I ran HFSLIP on the default compression with no multi-boot CD option. Any ideas as to what is going on? I admit I'm not very technically knowledgeable, but I will do my best to provide any information needed to figure this out. EDIT---one last experiment before bed---I found HFSLIP 1.7.9 beta m on my backup drive and ran all of my current slipstream files through this old version. The files processed fine with no errors (presumably; I haven't actually tested the resulting ISO). So I think that means that there is something fishy with the latest beta (1.7.10 J) and not with any of the files or hotfixes themselves?
  5. Well, an update: I made a .cab using the LegitCheckControl (1.9.40.0) from the site off of -X-'s sig, changed the version number in the .inf file from the old .dll to match the new .dll, and slipstreamed the new .cab in. Works a treat, and I'm no longer getting bugged about KB892130. As for KB905474, I've decided that I'm not even going to install this file anymore, so I'm not gonna worry about that one.
  6. Acheron's .inf worked for dealing with KB905474. Huh, so is the KB905474 problem specific to HFSLIP, then? The long WGAN/BK905474 thread seems to indicate that there is new code in the latest version that HFSLIP is not handling properly? Sorry if this has all been asked before; I know very little about this sort of thing. >.< As far as KB892130 goes... now that it's been mentioned, 1.9.40.0 sounds familiar... I seem to recall having downloaded this version at some point, but I had like 5 different WGANs floating around at the time, trying to figure out which one to slipstream, and now I can't find it again. Might someone be so kind as to provide a link to this latest version? I cannot find it for the life of me.
  7. I also have the same problem with KB892130 and KB905474; I will try Acheron's fix and report back. As far as KB892130 goes, rooting around in the SoftwareDistribution folder seems to indicate that Microsoft Update is preferring version 1.7.69.2 of legitcheckcontrol.dll instead of 1.9.9.1. That's the version that is flagged as missing via website updates, anyway. Maybe a problem on their end?
  8. Latest beta worked perfectly. I did a very vanilla slipstream, and there were no problems at all. Great work, everyone!
  9. I just did a fresh install about 4 days ago; KB951748 shows up in Windows Updates, so yes, I think it's needed.
  10. Nope, no problems with the program in SP2. No problems with the program in an untouched SP3, either. Now that I think about it, I reduced components more aggressively in my SP3 install (since I'd gotten used to nLiting... well, a little bit), so if I went back to reducing and removing the same components in my SP3 install as I did in my SP2 install, the image editor should still work fine. This of course doesn't satisfy my curiosity, lol. I want to pinpoint the exact component that's causing the program's failure to launch, but short of tons of trial and error imaging and an extensive knowledge of Java, I don't know if I'll be able to find out.
  11. Hi all, thanks for the replies. The issue can't be related to the MSJVM because a completely untouched and untweaked install with SP3 slipstreamed allows the image editor to work perfectly. The second I start taking out or changing any of the default settings, the image editor refuses to work again. I'm wondering if anyone more knowledgeable than I am could explain to me how a Java environment is created in Windows? Clearly, I'm removing some component or turning off some service that's crucial for the image editor to create its Java environment, but I have no idea what the component might be. My suspicions at this point are that the culprit is either Smart Cards, the Teletext... thingy, the IE files (but not the core files), or some kind of service. But like I said, I know very little about Java, so I could be on the totally wrong track. Then there is the curious symptom of the image editor always being able to be run after the initial install, and then never again after. Is there any Windows component that could behave this way?---run when a program is being installed, and then never run as soon as said program is closed? Very puzzled and a bit frustrated. I could just leave the OS untouched, but... what's the fun in that? Thanks for reading!
  12. I'm using an image editor that apparently requires a function called either Java Virtual Machine or Java Advanced Imaging to launch. The wording of the actual error is "Java error: Can't create JVM." I'm not a power user, just like to use nLite to slim down the install and tweak the registry a bit, so I'm really not sure which component I removed that I shouldn't. I have used nLite to remove components many times before, with no errors from this image editor. The only thing I can think of is that this last time, I removed Internet Explorer, although I left the core files intact. Copious Googling and forum browsing has failed to determine how Internet Explorer files are related to Java. Would anyone care to explain that to me, or to explain what I might have done wrong? Have tried installing Java Runtime Environment from the Sun Microsystems website, to no avail. Don't even know if that is relevant, in this case. Interesting symptom is that when the photo editor is first installed, it works fine. As soon as the system is rebooted, it refuses to launch forever after. Running XP SP3, nLiting XP SP3. Any help or input would be appreciated. Thanks much!
  13. Nevermind, I figured it out. Lol.
  14. Just created an unattended disc with 1.7.8 today, and apparently this hotfix is refusing to be integrated again. I checked the MS Security Bulletin, and apparently they've "updated the update." Here's the link to that: http://www.microsoft.com/technet/security/...n/ms08-030.mspx Is this in fact an updated update? Any new tricks to force this to integrate, or should it be just treated as another HF and placed in the HF folder?