ISO too large.

[Meadow]

Please forgive the lack of technical terms, but I'm very much an amateur technician. A considerable amount of my expertise is down to pointers from friends and trial and error.

My daughter's partner presented my with an Eee PC 901 which was clogged up with rubbish. I exported the program files into D: and set up a mount from C: However I found that Windows was taking over the miniscule sub 4GB C: drive.

In the end, I chose to reinstall Windows which was a big mistake - too big for the drive. So, of course the drive has been formatted. By chance I happened on this blog. I followed the instructions given and was a bit surprised to find the ISO coming out at over 2.3GB. We included some components that the blogger didn't recommend - a handful of MB worth. We were therefore surprised when the ISO came out at over 2GB. Of course, a set of data that big would only fit on a DVD, not a CD, and Eee netbook just won't recognise a DVD.

The original Windows disc is a Dell Windows XP Pro Media edition.

I can't provide screen shots as I only have the ISO, and have no idea how to view the contents.

Any pointers as to where I've gone wrong would be really appreciated.

I may have posted this to the wrong section, so I'll re-post in Nlite.

[Guest]

johnhc had a very similar problem...

[Meadow]

johnhc had a very similar problem...

I'm afraid that makes no sense to me. Please consider me a complete novice (oh the embarrassment). all I know is that in all likelihood, there's a possibility that the i386 files should have been included, but why the massive (from memory) OEM files?

Sorry to be pushy, but this netbook is due to head back to Scotland in 30 hours, and I really hate to admit defeat. I can do the work if someone would be so kind as to walk me through the process. At present the Netbook has an incomplete version of Windows, and won't boot up as a consequence. I really can't work out why these machines have such a small C: drive, it's pointless.

[Guest]

I'm sorry. I didn't realize there is a time constraint.

Long story short, choose the Mkisofs ISO engine in nLite.

[johnhc]

5eraph, I don't think using a different ISO creator will help. I think Meadow needs a smaller ISO.

Meadow, unfortunately there are a number of questions. Are you using nLite? Is the Windows source a recovery CD? Did the CD come with the Eee? I suspect you are in a bind because I suspect the CD is not for the Eee and it may not be legal to install it on the Eee. Please tell us where the CD came from and if you have a CD that came with the Eee. We will take a look, so, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

[jaclaz]

Meadow double posted, here is the rest of the story:

http://www.msfn.org/board/have-gone-wrong-t140439.html

jaclaz