JerichoJones

Member
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JerichoJones

  1. When doing multiple builds nLite is difficult to manage because it uses the presets directory AND the LAST_SESSION.INIs cannot be distinguished except by date/time. I don't know about you guys but I can't remember the date and time that I worked on my WinXP build as opposed to my Win2K3 build. If the LAST_SESSION.INI was read from the OS build directory upon loading it would solve the problem. I don't understand how people creating multiple builds could think that using nLite\presets directory is a better idea. Please enlighten me. If LAST_SESSION.INI was appended with the OS build directory name that would be helpful if nlite\presets must persist.
  2. BUMP
  3. Any chance we could change the default location of the LAST_SESSION.INI to be the OS build directory instead of nLite's installation directory? I am trying to manage multiple builds and sometimes I forget to load the INI file from the OS build location.
  4. I'll stick with 1.0.1 for now. Thanks nuhi! jj
  5. OK. I went back to 1.0.1 and the problem went away. Looks like a bug.
  6. I have been getting the "Access is Denied" error on first boot under Win2K Svr(Win2K3 works fine). After a lot of research I have narrowed it down to what appears to be a permission error in the registry. HKLM,"Software\Microsoft\Windows\CurrentVersion\Installer","InstallerLocation",0x00000000,"%10%\system32\" Issues: This key is set to NOT inherit perms ADMINISTRATORS perms are defined as READ ONLY on this key ONLY (no downlevel inheritance) SYSTEM perms are defined as FULL CONTROL on this key ONLY (no downlevel inheritance) I looked at an out of the box Win2k Svr install and the perms should be: This key is set to NOT inherit perms ADMINISTRATORS perms are defined as FULL CONTROL on this key and subkeys SYSTEM perms are defined as FULL CONTROL on this key and subkeys EVERYONE perms are defined as READ ONLY on this key and subkeys nuhi! HELP!!
  7. Check this link: http://www.experts-exchange.com/Operating_...Q_20790028.html Good Luck!
  8. Sorry. I guess I wasn't clear. When I build the image on a laptop with SATA, the image works fine in a VM or hardware with ATA. At least it works under XP. Under Win2k it does not. The drivers are the HP (Intel) SATA drivers.
  9. OK. So why does Ultra DMA work if I did not create the image from that? I'm confused.
  10. I am using nLite to create build cd from which I can create a unified ghost image. I have no apparent issue with the integration into the cd. Here is the problem, I build my image in a VM and it seems fine until I try to boot on a machine with the SATA hardware (Inaccessible_Boot_Device). If I load the OS from nLite CD on the SATA hardware and create the image it works great on all my hardware. I want to develop my image in a VM. How can I solve this problem?
  11. I have the autoinstall working but I have two issues: 1. I don't want it to scan the hard drive during the install. 2. Can I use the SERVERGROUPNAME property to force the Group membership?