xpfromcd - "no space on disk error" when there is plenty of space
Submitted by Krunoslav on November 12, 2006 - 5:33am.
LivePC 1.0.7263.0 beta, latest xpfromcd tried from root of usb drive and root of c:\ with the same results.
LivePC installed on USB 2.0 flash key with 3.8GB.
The following might be relevant:
1. I have VMWare 5.5.1 installed
I tried to create an XP Pro engine from XP CD.
When I run start.bat, put the XP CD into CDROM drive, enter the key and the details, a few messages later in the command window I see that xpfromcd tries to use the temp directory
at c:\documents and settings\....\temp and complains that the directory does not have 1300MB required, but it has gigabytes.
It asks me to specify another directory and I do with the same results. Installation not possible.
Two comments:
1. Has anyone programming this heard of the environment variables? My temp directory happens to be specified in another location in TEMP and TMP environment. It would have been preferable to use this instead of c:\documents and settings\...\temp.
2. Complaining there is no space when in every case there are gigabytes of space is a putoff. I seriously doubt that I would be able to proceed with installation down the line without more serious bugs when even at the beginning something trivial stops the process.
hi
Submitted by FX Fade on November 24, 2006 - 11:47am.
is there already a fix for this issue? i use a german version of xp on hostmachine and to install...
Working on it
Submitted by Ramesh Chandra on November 24, 2006 - 8:01pm.
Hi,
We are looking into this issue and will let you know once we resolve it.
Thanks for using the LivePC Engine.
-Ramesh.
Hello,
Hello,
Sorry you are having problems with the xpfromcd script. By any chance are you running a non-US-English version of Windows XP? There is a known problem for the xpfromcd script when running on non-US-English Windows XP or when you customize the digit grouping symbol. It will be fixed in the next release. Please let us know if you are using a US English version but still get the error, as we haven't seen that problem before.
We'll also add support for using the TEMP environment variable in the next version. Thanks for the suggestion.
-John