Rhor Posted May 29, 2007 Posted May 29, 2007 Greetings everyone.Everything is good and pretty when I use nLite 1.3.5 or earlier versions until I get to the point when I have to create the ISO to be used on a Virtual Machine. Since I use $OEM$ folders, I have filenames that are correctly named, but when the ISO creation process starts, somehow everything changes to capital, and I mean everything, even my files on the $OEM$ folders.Is there any problem with the way I use nLite or there is a workaround this problem?.Thank you kindly for your responses.Last_Session.ini
nuhi Posted May 29, 2007 Posted May 29, 2007 Well it will just upcase root and i386/amd64, not inside the $oem$, please confirm.If you want to avoid this then use some other tool just for the last step, the ISO creation, it does it when you press the Make ISO button, all the processing before that is fine regarding that.
Rhor Posted May 30, 2007 Author Posted May 30, 2007 Thanks for the answer Mr. Nuhi.The change affect the inside of the $OEM$ folder as well, and since I have inside of it predifined shortcuts for the desktop and similar things, I do mind the capital letters.I used CDImage with a "boot.img" that I found on MSFN to create the image file, and when tested on the virtual machine, it installs fine, but when it tries to log in for the first time, a blue screen appears very fast and it then reebots itself.I can use any other tool, but I have always used nLite for the entire process, so thats why I was wondering what was the problem with this lastest releases, if theres one.Thank you.
nuhi Posted May 30, 2007 Posted May 30, 2007 I'll check the capitalization of $oem$ before the next update.As for the BSOD it's probably because of integrated textmode driver, like SATA controller.Be sure to integrate your chipset drivers as well. Also you could find some info here:http://www.msfn.org/board/index.php?showtopic=51140Let me know how it goes and which drivers.
Rhor Posted May 31, 2007 Author Posted May 31, 2007 Thank you again for the responses Mr. Nuhi.I resolved the problem of the BSOD. It appears to be a new addon pack that I started to use, the Gmail Drive addon pack. I had a feeling and I left it out, then everything worked just fine. I used again CDimage for the ISO creation, and the vistual machine worked fine as well.Please check the capital letters problem for the next revision, I just hope is something I'm doin wrong, because I dont see anyone else having the same kind of trouble.Thank you for your patience.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now