dagon

Member
  • Content count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dagon

  1. this is an interesting topic ive read through most of the 8 pages and pretty much understand what the purpose and point to all of this is.. but i honestly don't recall after going through the 8 pages if this question/thought is answered (ive been at work all night, and have been drinking some very alcoholic beverages since i came home, so i dont recall too much of what ive read) : what is the purpose or significance of needing or the requirement to have a "holographic" CD from the factory? if using this method produces four required files (not including the winnt.sif here, only the oembios.* files) could these files be used in a generic OEM cd to essentially recreate the pre-activated installation? by "generic" i mean an ISO created from one of the forementioned 9 in 1 or 11 in 1 "warez" internet releases. are there other modified files on the factory cd that are required to make use of this function that would not/may not be present on a generic cd? i only ask this out of educational interest and not because i am trying to anything "illegal". i have a brand spanking new Dell system that has come with an XP reinstall CD, but i have not used it nor do i know if it "restores" the activation or if it is a straight XP install disc that I would have to use my COA key on or if it is built in with the SLP key. i had already started to test the "9in1" OEM ISO with these oembios.* files when I got to the page in the thread that said it would not work in a virtual machine since the VM's bios would not match. I dont want to waste CDR's and my already-activated system by testing to see if the 9in1 OEM would work or not.. don't ask me why I didn't just make an ISO of the restore cd, there's no answer for that... i just didnt. as i write this lengthy post, i'm testing this method on my Toshiba laptop using the oembios.* files from it and the SLP key to see if it comes out pre-activated or not. second question how does using this method differ or how is it different than the "OEMScan - Automated Multi Manufacture Pre-Activation Utility" thread? or does it not differ? from the sound of it both methods get the SLP key, and create the oembios.* files... is this correct? Ultimately what I want to accomplish is to be able to create a custom install CD using nLite/etc that is already activated--which normally would not be possible unless you started with a VLK source/key--on my laptop (which legit coa, slp, etc) and my Dell desktop (ditto on the legit). I have a restore cd for the Toshiba that restores it to factory, including the activation, but also including all the junk software. And as I said, I'm not sure what the Dell restore CD is... if it's just a straight XP install of it its an actual "restore" cd.. Sorry for the long winded post, I tend to blab on and on when I've been drinking. Thanks. -- Edit The Toshiba reinstall using the generic OEM cd is not accepting the SLP key. Dont know if I did something wrong or not (and ive wasted a cdr on this). Looking at the Toshiba restore CD its a ghost image so it would not be easy to work with.
  2. Is there a way to disable the ability to format drives without setting any kind of user account restrictions or something like that? I'm looking for a registry key that can be toggled on/off or something like that. The reason: If I have an encrypted drive that is not mounted the drive is shown in explorer but if you try to access it it says it is not a valid partition and asks if you want to format it. I don't want to have the chance that the drive will get formatted accidently by anyone using the computer, destroying my encrypted data. nLite has a modification to disable the format support, but I dont know how it is implimented, or if the method it uses could be toggled on/off.....
  3. Looks like I found my problem at least... I had SFC disabled, and additionally I added these files to the remove box: sfc.dll sfc.exe sfc_os.dll sfcfiles.dll Apparently that was causing my lsass.exe failure. I took those files out of the remove box and now it is installing as it should.
  4. I think I might know what your problem is. I too have been having this same problem after doing a pretty scaled down version of XP with nLite. One thing you may not have seen is the message box that is appearing right before the computer reboots. If you have in fact removed the same process as I did, this could be your problem. I tested my nLite ISO in VMWare and found this problem, as the actual installation was too fast for me to see the message box text. The problem: lsass.exe is failing. I have not looked into the solution yet. Check out this video (not sure if it will work, it's not playing for me) of my VMWare movie capture and see if it is the same for you http://www.zippyvideos.com/482840012718908...essional_movie/ here's another of the video, dont know if this will work either http://www.picserver.nl/v/AZD6F152WDVB