Jump to content

Waldo2k2

Member
  • Posts

    6
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About Waldo2k2

Waldo2k2's Achievements

0

Reputation

  1. I can confirm with 1.4 rc2 that this is no longer an issue for me. Not sure what caused it with that version.
  2. FYI, Vanilla = Clean...sorry, it's a term used elsewhere to describe a clean source...didn't mean to confuse the subject. I noticed there are 2 rc's in the last couple of days, I will test with the latest and post results back here.
  3. Well I'm not Nuhi, but I can guarantee that nlite didn't mess up your computer. You said yourself it's a computer you just built, did you try checking the cables? SATA cables tend to fall out easier than ide (from experience). It is also possible you happened to get a bad dvd drive/cable/motherboard...I would check out those things first. Good luck.
  4. Using Nlite 1.4 beta, changing the usb polling frequency causes windows setup to fail every time (missing or corrupted usbehci.sys error). Conditions: Vanilla XPSP2 disc + Nlite usb polling option only Results: Fatal setup error: Missing or corrupted usbehci.sys Test System: VMWare Server Fix: Not selecting a different usb polling freq. resolves the problem. This problem was kicking my butt for hours last night, I tried every combination of order of operations for rvm updates and driverpacks, eventually I narrowed it down to something with nlite, then finally the light bulb turned on and I made the connection between the faulty usbehci and the polling option. Hope this helps, if you need my log I can post it, but I don't see any sense in running the process all over again when it's easy enough to test the outcome. Thanks for great software.
  5. Very sorry for that, I tried both. Do you need an other info?
  6. I've tested this in 1.3RC, 1.3beta, and 1.2.1 stable and it's the same outcome with all three. Situation: Using a mapped drive to a samba share (permissions 777, owner: samba user) that contains the xp sources. Outcome: Using the latest AutoImage, RVM and DPB integrate just fine, nLite doesn't do anything. It just closes after "Preparing Selected Tasks". The nLite log only shows the settings I used, no errors. Using the EXACT same AutoImage ini I integrate the same sources, only this time they're located on a local drive and it works splendidly. ::edit:: forgot to mention that if I reopen the sources with nLite after it fails, it complains of a broken nLite something or other (basically stating that it didn't work on those sources) Other notes: Originally I put the source installation files onto the samba share from the server itself...this resulted in my linux box account being the owner of those files, which made nLite complain that there "wasn't enough space" when selecting the sources (this behavior was the same in 1.2.1, 1.3b, 1.3RC). So by copying the source files to the samba share from my windows box, my windows user (effectively samba user on the linux box) was the owner of the files and could change permissions (such as removing any read-only flags). That is why I believe it threw the not enough space error. Possible Causes: Samba user was not the owner of the containing folder in which the source files resided...possibly this is what made nLite unhappy? Perhaps this is isolated to samba shares on linux servers? It would be interesting to see if someone experiences the same issues when working with a samba share hosted on a windows box...
×
×
  • Create New...