I386 renamed to Application Data

[matt79]

I have a I386 from a friend who wants to do a clean install on there computer. The version is XP home edition. I normally use nLight to created a bootable ISO and then burn it to a disk. However, when I burn it to a disk nLight for some reason renames the I386 to application data. So if I open and view the files inside the newly created disk there are only WIN51IC and application data. If I open application data I see the files that where in the I386 folder.

Has anyone every seen this before? and did they find a way around it?

Thanks,

Matt

[GrofLuigi]

Hi and welcome,

Please attach (don't paste) your Last Session.ini (as seen in the red letters above ). Only Last Session.ini please and don't paste it.

GL

[johnhc]

I have a I386 from a friend who wants to do a clean install on there computer. The version is XP home edition. I normally use nLight to created a bootable ISO and then burn it to a disk. However, when I burn it to a disk nLight for some reason renames the I386 to application data. So if I open and view the files inside the newly created disk there are only WIN51IC and application data. If I open application data I see the files that where in the I386 folder.

Has anyone every seen this before? and did they find a way around it?

Thanks,

Matt

matt79, this whole description makes little sense to me. Where did your friend come up with such a thing? Is it a legal copy of XP? If not, we cannot talk about it here. Please post a screen shot of a Windows Explorer view of the original CD and the nLited folder. Enjoy, John.

[matt79]

I have a I386 from a friend who wants to do a clean install on there computer. The version is XP home edition. I normally use nLight to created a bootable ISO and then burn it to a disk. However, when I burn it to a disk nLight for some reason renames the I386 to application data. So if I open and view the files inside the newly created disk there are only WIN51IC and application data. If I open application data I see the files that where in the I386 folder.

Has anyone every seen this before? and did they find a way around it?

Thanks,

Matt

matt79, this whole description makes little sense to me. Where did your friend come up with such a thing? Is it a legal copy of XP? If not, we cannot talk about it here. Please post a screen shot of a Windows Explorer view of the original CD and the nLited folder. Enjoy, John.

I know it makes little sense that is why I can not figure it out. It is legal copy of windows xp. The I386 folder was shipped on the computer from dell. I am at work right now so I can not post a screen shot. I will try to later.

[johnhc]

I know it makes little sense that is why I can not figure it out. It is legal copy of windows xp. The I386 folder was shipped on the computer from dell. I am at work right now so I can not post a screen shot. I will try to later.

matt79, this may be a recovery folder. Please do some searching for nLite and Recovery CDs. Google seems to work better that the MSFN search. Just go to Advanced and specify the MSFN site to search. Enjoy, John.

[matt79]

I know it makes little sense that is why I can not figure it out. It is legal copy of windows xp. The I386 folder was shipped on the computer from dell. I am at work right now so I can not post a screen shot. I will try to later.

matt79, this may be a recovery folder. Please do some searching for nLite and Recovery CDs. Google seems to work better that the MSFN search. Just go to Advanced and specify the MSFN site to search. Enjoy, John.

Would the I386 folder on the hard drive be considered recovery? That is the only files/CDs that he has from dell other than drivers. In the past I just used nLite to make the I386 folder bootable and burned it to a cd. But that was with XP pro.

Everything seems to work the same when I do the home edition but when I try to boot from the newly made cd it says "NTLDR" file could not be found. So I put the new CD in a computer and view the files/folders on it, and there are two, One "application data" folder and "win51ic" file. Inside the "application data" folder there is the "NTLDR" file. But normally NTLDR is inside the I386 folder, so I am assuming that is why it can not boot from the cd.

[johnhc]

Would the I386 folder on the hard drive be considered recovery? That is the only files/CDs that he has from dell other than drivers. In the past I just used nLite to make the I386 folder bootable and burned it to a cd. But that was with XP pro.

Everything seems to work the same when I do the home edition but when I try to boot from the newly made cd it says "NTLDR" file could not be found. So I put the new CD in a computer and view the files/folders on it, and there are two, One "application data" folder and "win51ic" file. Inside the "application data" folder there is the "NTLDR" file. But normally NTLDR is inside the I386 folder, so I am assuming that is why it can not boot from the cd.

matt79, I have never personally encountered a recovery disk/partition, so I don't really know if this is Dell's way of doing recovery. I do know that some here have had success with Recovery CDs and some have not. That is why I suggested that you do some searching. Why nLite would rename the I386 folder to application data is beyond me. Just for the fun of it, try renaming the folder back to I386, create an ISO then test on a virtual machine. VMs are the best way to test these kinds of things. VMware Player, VirtualPC and VirtualBox are all free. Please let us know what you learn and be sure to attach your Last Session.ini. Enjoy, John.

[matt79]

Would the I386 folder on the hard drive be considered recovery? That is the only files/CDs that he has from dell other than drivers. In the past I just used nLite to make the I386 folder bootable and burned it to a cd. But that was with XP pro.

Everything seems to work the same when I do the home edition but when I try to boot from the newly made cd it says "NTLDR" file could not be found. So I put the new CD in a computer and view the files/folders on it, and there are two, One "application data" folder and "win51ic" file. Inside the "application data" folder there is the "NTLDR" file. But normally NTLDR is inside the I386 folder, so I am assuming that is why it can not boot from the cd.

matt79, I have never personally encountered a recovery disk/partition, so I don't really know if this is Dell's way of doing recovery. I do know that some here have had success with Recovery CDs and some have not. That is why I suggested that you do some searching. Why nLite would rename the I386 folder to application data is beyond me. Just for the fun of it, try renaming the folder back to I386, create an ISO then test on a virtual machine. VMs are the best way to test these kinds of things. VMware Player, VirtualPC and VirtualBox are all free. Please let us know what you learn and be sure to attach your Last Session.ini. Enjoy, John.

Yeah I use VirtualBox, it has saved me alot of money since I do not have to physically burn a CD :-). I have the PC now so I am going to look into the matter some more.

[matt79]

Here is an photo of what I am talking about. The one on the left is the ISO open in Alcohol and the one on the right is the iso open in virtualbox. The virtual box is running XP home. It is the same image opened at the same time on both. I include "Last Session.ini" also.

Now I do not know if this has anything to do with it but the original I386 folder did not have an "NTLDR" file. So I just took one off of another windows xp home disk and put it in the folder.

Last Session.ini

Edited August 24, 2010 by matt79

[johnhc]

Here is an photo of what I am talking about. The one on the left is the ISO open in Alcohol and the one on the right is the iso open in virtualbox. The virtual box is running XP home. It is the same image opened at the same time on both. I include "Last Session.ini" also.

Now I do not know if this has anything to do with it but the original I386 folder did not have an "NTLDR" file. So I just took one off of another windows xp home disk and put it in the folder.

matt79, thanks for the Last Session. First you are running nLite under Vista (or W7) to create an ISO for XP. This will not work when a Service Pack is integrated, which you have done. I have never seen the Application Data name for the I386 folder before and assume it has nothing to do with using Vista. It is best to use XP to run nLite. You can do this under VPC, if you don't have an XP system to use. Please go to Google and paste 'nlite "recovery partition " site:http://www.msfn.org', without the single quotes into the input line. You will get many good hits and hopefully some real help. Enjoy, John.

[matt79]

Here is an photo of what I am talking about. The one on the left is the ISO open in Alcohol and the one on the right is the iso open in virtualbox. The virtual box is running XP home. It is the same image opened at the same time on both. I include "Last Session.ini" also.

Now I do not know if this has anything to do with it but the original I386 folder did not have an "NTLDR" file. So I just took one off of another windows xp home disk and put it in the folder.

matt79, thanks for the Last Session. First you are running nLite under Vista (or W7) to create an ISO for XP. This will not work when a Service Pack is integrated, which you have done. I have never seen the Application Data name for the I386 folder before and assume it has nothing to do with using Vista. It is best to use XP to run nLite. You can do this under VPC, if you don't have an XP system to use. Please go to Google and paste 'nlite "recovery partition " site:http://www.msfn.org', without the single quotes into the input line. You will get many good hits and hopefully some real help. Enjoy, John.

I am using W7 pro. I know it says I integrated a service pack, but I did not. I will try to do the I386 with nLight in an XP pro virtual box machine and see if it comes back better.

Thanks,

Matt

[jaclaz]

I am using W7 pro. I know it says I integrated a service pack, but I did not. I will try to do the I386 with nLight in an XP pro virtual box machine and see if it comes back better.

Thanks,

Matt

Once solved the Windows Vizta :ph34r:/7 compatibility issue, the problem is most likely in the crap DELL has added/modified to that specific I386 folder.

Even for making a PE DELL's builds are reknown to create havoc.

It is as well possible that the Servicepack is already integrated.

A longer, but maybe necessary approach, check the files:

http://www.msfn.org/board/index.php?showtopic=91907

jaclaz

[matt79]

Well I tried to create the ISO from the I386 folder on a virtual box XP pro machine. However, it is still being labeled "application data."

[johnhc]

Well I tried to create the ISO from the I386 folder on a virtual box XP pro machine. However, it is still being labeled "application data."

matt79, that is what I assumed. Please try the Google search. Have you tried renaming the 'application data' folder to I386 and creating an ISO? Enjoy, John.

[matt79]

Well I tried to create the ISO from the I386 folder on a virtual box XP pro machine. However, it is still being labeled "application data."

matt79, that is what I assumed. Please try the Google search. Have you tried renaming the 'application data' folder to I386 and creating an ISO? Enjoy, John.

How would I create the ISO? Normally I use nLite for that. Is there another way/program?