Jump to content

Troglodyte

Member
  • Posts

    32
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Troglodyte

  1. Hi, I have been having problems with an nLited installation of Windows XP x64 SP2. After being unable to install .NET 3.0, and many other applications which seem to just hang, I went to work to discover which component removal was causing this problem. After many hours I found that removing the "Net Logon" service causes this issue for some reason. I am not certain if it breaks "Windows Installer" persay, but for certain it makes it impossible to install any version of .NET and a few other driver installation programs were also hanging. Just wanted to pass this information along to nuhi or anyone else. Thanks
  2. This release is very much appreciated. Merry Christmas and Happy Holidays to you as well
  3. I don't have much free time anymore because of an intense College schedule... but this trick I discovered myself back in 2004 may work. It concerned Windows 2000, but it may work for Windows XP as well. Click this link to go to the page in which I described my discovery: can any one here help with this problem Let me know if it works for you... I'm curious and hopeful that it might.
  4. I have also confirmed this using the latest nLite (1.2RC) and Windows 2003. So maybe this should be added to the compatibility options of "Windows Update" in the next version.
  5. OK... thanks nuhi. That makes sense. However, interestingly if File Printer and Sharing is left installed and not removed by nLite... and then removed later by hand while in windows, this error does not result. I am not at home to confirm this, but I assume that the LanmanServer is left intact if you remove File and Printer Sharing while within Windows. Also, this error doesn't result when removing File Printer and Sharing on Windows XP or XP x64 using nLite.
  6. Hi, I have tested using the latest nLite (1.2RC) along with a copy of Windows 2003 Standard (32bit with SP2 Beta Refresh 1 version 2786) manually slipstreamed together. After much testing I have discovered the source of a problem I have been having using nLite with it. Choosing the option: Unattended -> Network Settings -> File and Printer Sharing and selecting Disabled, results in the following error on startup (just before login): Service Control Manager --------------------------------------- At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details. Looking at the event log, it yields the following error under system: Source: Service Control Manager Event ID: 7003 Description: The Distributed File System service depends on the following nonexistent service: LanmanServer I have recreated the error several times by doing what I just described. So I guess you could call this a bug report... manly I just wanted to pass this info onto nuhi. I think I have provided enough information, but if you need more just let me know. Thanks.
  7. nVisiLite Not sure... this is a difficult one to name. Either way, I'm very pleased to see you have been working on it, and that it will be a separate program. As I think that is the wisest decision. No matter what its called I'm sure it will be great. I will never fully adopt vista unless I can trim down all the fat. So thanks.
  8. Thanks... although I tried searching the forums again... and I still can't find it lol Either way... one way of getting it is good enough for me. I'm going to play dumb and blame my stupidity on not having a clear head due to being sick. Anyway, thanks again
  9. I hope its OK to ask this... But where is this 2.12a release of RyanVM's update pack anyway? I don't see it listed anywhere on his site, or on the forums. I only see version 2.12 of the update pack. Thanks
  10. @gelcode Sure... for most of it relating to creating an "Unattended CD." MSFN's own Unattended XP Webpage should do the trick nicely
  11. @gelcode Don't worry about... I have just found that my instructions are now outdated and obsolete, lol. Now that the new version has been released, I just tried it... and believe it or not, it will run fine on Windows 2000 SP4... it correctly replaces all icons and sounds, etc. I was suprised... that means that this can be OS independent and work without the complicated instructions I described (with using BatchMod). Now instead of what I described you should be able to do the following. Copy the FlyakiteOSX v1.0.exe into the "$OEM$\$1\FlyakiteOSX" folder for your unattended CD. Now that this is done... you need to add the following bit of code as the last line of your INSTALLS.BAT file that is inside you $OEM$ folder ECHO Beginning BatchMod Install ... START "BatchMod" /WAIT /MAX /HIGH "%SYSTEMDRIVE%\FlyakiteOSX\FlyakiteOSX v1.0.exe" Or you might be able to get the executable to run directly off of the CD, which would be even better... so you could try that. I have not tested this yet... but I see no reason that this should not work. Good Luck, and let us know
  12. @gelcode I think I will share my secrets with you. You seem to be trying to do the same thing that I have already set up. One of the great things about "my method" is that it is OS independent, I even use it with Windows 2000 SP4, although some of the icons look a bit ugly because of the lack of alpha blending. Anyway, I will do my best to explain the steps. Firstly, you need to extract the Flyakite archive... to do this, during installation choose the 'Extract Files Only' install type and the installer will extract all of the files to a directory of your choice instead of installing them. Then I think you will see a folder for BatchMod. This is what you need. Copy it into the "$OEM$\$1\BatchMod" folder for your unattended CD. In the BatchMod\_OUT folder you will need to have the replace.txt file. I can't remember if I made this myself, or if it was provided. But I can give it to you, if you need it. However, it has been a while since I updated this process, and it is still based on SP1 files. The following folder should be left empty: BatchMod\_IN BatchMod\resources BatchMod\logs (I think this folder can be empty also) Inside the BatchMod\_SOURCE folder is where you should put all of the OSX related EXE's, DLL's, and CPL's. Inside the BatchMod\js folder should be the copy.js, extract.js, and modify.js files. Under the BatchMod\tools folder should be two subfolders named Replacer and ResHack. Under the BatchMod\tools\Replacer folder should be the following files: data db.csv readme.txt Replacer.cmd Under the BatchMod\tools\ResHack folder should be the following files: ResHacker.exe ResHacker.ini Now that this is done... you need to add the following bit of code as the last line of your INSTALLS.BAT file that is inside you $OEM$ folder. ECHO Beginning BatchMod Install ... START "BatchMod" /WAIT /MAX /HIGH "%SYSTEMDRIVE%\BatchMod\auto.cmd" This will execute BatchMode and replace your files as the last step of install.bat. Before it is executed though... I recommend removing the CD just in case WFP tries to grab a bunch of the files of the CD. I hope this helps. This may not be exactly what you are looking for... but it is closely related, at least enough for some one to get some useful information out of it I think. And if you do it this way... you can use it with any version of the Windows 2000, 2003 or XP OSs, without manually changing every file.
  13. @hp38guser Thanks.. yep... I got it now... I just didn't know where to look
  14. @hp38guser I hope I'm allowed to ask this... but where is everyone getting this file from? I have downloaded the evaluation of Windows Embeded... but I can't seem to find it anywhere. I hope that it can be downloaded legally, and if this is not the case... I am not asking anyone to post links of course. Thanks
  15. Troglodyte

    NAV2005

    I'm not here to argue, but... I personally think Norton is an incredibly bloated piece of software.... Our university has a corporate license... and often times it just ends up royaly screwing up machines and killing system performance. And I really don't think it does a good job at catching, and stoping viruses. I think that the best choice is Avast! Antivirus... even the free version is 100s of times better than norton. However, I do agree with the second part of your statement... Norton, does need pretty much "everything in place". This is because it is heavily reliant on services, and the internet explorer API... I tend to avoid products that "require" i.e., and this is definitly one of them of them... although there are many other reasons that I won't use Norton... but I won't bore all of you
  16. FYI: Just thought i'd point out that the problem still exists with nLite 98.6 using XP SP2 RTM (2180). Once again, all you have to do to generate the error is to select the firewire drivers for removal... or so it appears... because when I do not select them, and then compile, the error does not occur.
  17. Oh yes... thank God... I was going to say... that there would have been a lot of people mad at MS... uhm... let me rephrase that... more than usual
  18. I love firewire... its much better than usb... please explain what you mean by this... I would hate for it to be somehow crippled by MS
  19. FYI: I just experienced this same problem again with the newest version of nLite (98.5) using XP 2162. The service pack doesn't seem to have anything to do with it. All you have to do to generate the error is to select the firewire drivers for removal... or so it appears... because when I do not select them, and then compile the error does not occur.
  20. I don't think its related to SP version... as I am only using SP2 RC2 I could provide it... but I'm sure it won't help you, as I know you have access to SP2 RC2 (which is version 2149, I think)... Besides... I enabled a bunch of experimental feautures... but if you still need something from me... like my .ini... then just ask
  21. FYI: I just experienced this same problem when buiilding from XP SP2 RC2 using 98.4b. I too removed the firewire drivers... So I went back and tried again, this time not selecting the firewire drivers for removal... this fixed it I am pretty sure that this problem did not exist when removing the firewire drivers from version .97 through 98.3.
  22. @likuidkewl Boot Screen here... So you are one of the few people using Longhorn as the source with PE Builder? If so, how is it working?
  23. @superbikkel Thank you very much... I also want to say that you have done a wonderful job utilizing MS's WinPE... I think I can safely say that it would have taken me much longer to get my disc to this point if it wasn't for Bart and his pe builder. I will release my plug-ins soon enough... some of them are already available if you look hard enough. But only like 3-5 or so, and they are probably outdated by now. Let me clarify though, I didn't create ALL of the plug-ins that I have available on my distrubution, just many of them were created from scratch or heavily modified by myself. Many were gotten off the official forum, were I also post a lot. Sperbikkel, may I ask though, is there are particular reason that you are using the official MS's WinPE Builder? I don't think I would have the time or need to convert the plug-ins to MS PE format. I would probably leave that up to you. Of course, I would be glad to assist you any other way I could. Thanks for the compliments, Trog
  24. Here's Mine It took months of work... maybe its going at least a half a year of "development"... I'm not really sure... Its BartPE based using a slimmed down XP SP2 RC2 as the source (thanks to nLite 0.96.2) And yes, these pictures are real, and I have full sound and video working... Sorry about not releasing all of my plug-ins... I just haven't gotten around to it... and of course I haven't had time to write any real documentation... so it wouldn't be fare to release the more difficult ones yet... the screen captures themselves took a good chunk of time. I hope to have a real website soon, with small tips, plug-ins, etc... something that will do it justice, and help others out at the same time. I have to go to bed now... but I'l check back tommorrow morning at work... just to see how far your jaws dropped... just kidding
×
×
  • Create New...