Jump to content











Photo
- - - - -

FileCreateBlank - Failed to create a new file


  • Please log in to reply
4 replies to this topic

#1 Ramoondo

Ramoondo
  • Members
  • 2 posts
  •  
    United States

Posted 29 August 2010 - 02:25 AM

I'm attempting my first build of LiveXP with Winbuilder and I'm running into problems.

I've spent a few days studying the issue and several hours searching for solutions here. Forgive me if the problem has already been addressed and I somehow failed to catch the post.

A good ways in the build halts with this...


IF - File does not exist: [C:\LiveBuild\"C:\LiveBuild\I386\txtsetup.sif"] evaluated string: [If,NotExistFile,%TargetDir%\#1,FileCreateBlank,%TargetDir%\#1]



 FileCreateBlank - Failed to create a new file: [C:\LiveBuild\"C:\LiveBuild\I386\txtsetup.sif"] : The filename, directory name, or volume label syntax is incorrect. 

 Halt

My target build directory is "C:\LiveBuild\". Notice the nested references to it in the error.

Any clues? Link to log is here

#2 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 29 August 2010 - 02:43 AM

Highlighted is your problem:

IF - File does not exist: [C:\LiveBuild\"C:\LiveBuild\I386\txtsetup.sif"] evaluated string: [If,NotExistFile,%TargetDir%\#1,FileCreateBlank,%TargetDir%\#1]

FileCreateBlank - Failed to create a new file: [C:\LiveBuild\"C:\LiveBuild\I386\txtsetup.sif"] : The filename, directory name, or volume label syntax is incorrect.
Halt


You'll have to work out why you have "C:\LiveBuild" being replicated like that.

Regards,
Galapo.

#3 al_jo

al_jo

    Gold Member

  • Members
  • 1218 posts
  • Location:Tellus

Posted 29 August 2010 - 07:39 AM

Any clues? Link to log is here


Your source seems to be "Nlited".

If you remove the"C:\UBCD4Win\plugin\DriverPacks" from your build, you have the same result?

#4 Ramoondo

Ramoondo
  • Members
  • 2 posts
  •  
    United States

Posted 30 August 2010 - 08:24 AM

Yes Galapo, I thought I said as much. :ph34r:

al_jo: Actually I did try that. Now I get a similar error when it attemps to copy BCDW.ini.

Nested references to the target dir.

What I'm trying to do is create a build that will run off the first partition of an external eSata/USB hard drive with as many drivers and tools as possible to be used as an all-in-one diagnosis and repair tool with LiveXP as the platform.

I presume I want to use BootSDI as the image script, but I'm not sure how to get the build onto the partition correctly after it's done. Do I need a boot sector modifier or can I just point the bios to that drive?

On some of the builds I've tried, I get some of the files in the target dir and others in a Ram Drive dynamically created by the script. I'm not sure what I'm supposed to do with them after that.

There doesn't seem to be a way to just tell the script to build it directly onto the empty partition I have set aside for this task.

I've tried to cram everything I could into this one build (over 300 items to be processed when I click "Play"). I guess I should start with making it as simple as possible and working up from there.

#5 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 30 August 2010 - 11:12 AM

Hi Ramoondo,

A few things:

1. Don't use an nlited source as such sources produce unpredicatable results.
2. Don't insert a whole package of BartPE plugins (eg ubcdwin package).
3. NEVER use driver BartPE plugins with the InfSupport script (the script is only meant for apps).
4. I have no idea why it is reported that "Lancelot" has certified all those scripts. That's an error, so there's either some InfSupport bug or WinBuilder bug.

Best thing to do if you want to include these apps is to follow your advice, start small and work your way up:

I guess I should start with making it as simple as possible and working up from there.


Regards,
Galapo.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users