MSFN Forum: Nlite fails working with mapped drive - MSFN Forum

Jump to content



If you are having issues with Windows after removing components and have come to ask for help, please attach (not paste) your Last Session.ini file to your post to facilitate quicker assistance.
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Nlite fails working with mapped drive Rate Topic: -----

#1 User is offline   Waldo2k2 

  • Group: Members
  • Posts: 6
  • Joined: 14-January 07

Posted 14 January 2007 - 11:33 AM

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...

This post has been edited by Waldo2k2: 14 January 2007 - 11:35 AM



#2 User is offline   Speeddymon 

  • Advanced Member
  • PipPipPip
  • Group: Members
  • Posts: 323
  • Joined: 04-September 06

Posted 14 January 2007 - 12:24 PM

View PostWaldo2k2, on Jan 14 2007, 11:33 AM, said:

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...

The one thing you didnt mention (except in the title, which is why I am asking) is whether you tried this with an actual mapped drive that has a drive letter on your machine, or just a samba share that doesnt have a drive letter..

#3 User is offline   Waldo2k2 

  • Group: Members
  • Posts: 6
  • Joined: 14-January 07

Posted 16 January 2007 - 07:04 PM

Very sorry for that, I tried both. Do you need an other info?

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy