Jump to content











Photo
- - - - -

Questions about USB multi-boot 10


  • Please log in to reply
5 replies to this topic

#1 spacepure

spacepure
  • Members
  • 3 posts
  •  
    China

Posted 12 February 2009 - 10:04 AM

After I installed the USB multi-boot 10, and lauch the file USB_MultiBoot_10.cmd, It says that "ERROR File $OEM_X is missing" and cannot proceed. Has anybody encounter the problem? and How to solve it? Should I copy some files to certain directories before ? Thanks for your help

#2 wimb

wimb

    Platinum Member

  • Developer
  • 3756 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 17 February 2009 - 05:51 AM

After I installed the USB multi-boot 10, and lauch the file USB_MultiBoot_10.cmd, It says that "ERROR File $OEM_X is missing" and cannot proceed. Has anybody encounter the problem? and How to solve it? Should I copy some files to certain directories before ? Thanks for your help

$OEM$_X Folder is an empty folder being part of the USB_MultiBoot_10.zip download.
So I advice you to download again, may be there are more missing files in the archive that you are using now.
Download Direct from CD Forum: http://www.911cd.net...t...ost&id=1054

#3 elinap

elinap
  • Members
  • 2 posts
  •  
    United Kingdom

Posted 28 July 2009 - 09:33 AM

About usb_multiboot_10: (to WIMB - AUTHOR)
I am trying to create a bootable usb from a windows xp machine SP3.

The problem I am finding is that the script does not show a list of the drives in the computer. What I get when running the script is at first is:

find: 6.0.: No such file or directory
FIND: Windows NT: No such file or directory
FIND: invalid predicate `'
Press any key to continue . . .

Then, the main screen appears. But, when I select option 2 to select the USB drive, it does not show a list of the drives.

I have tried another script (by the same author): DriveList_XV.cmd, and it works ok. Can not find what is the difference between them...

Any suggestion/help would be appreciated.

Please cc replies to napchan@gmail.com
Thanks.

Eli

#4 wimb

wimb

    Platinum Member

  • Developer
  • 3756 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 29 July 2009 - 03:25 PM

@elinap

Strange difference ....

Can you try FIXPATH.exe
More Info: http://www.msfn.org/...o...112627&st=2

What do you get when you open cmd window and give VER and then [Enter] key ?

Are find.exe and findstr.exe present in C:\WINDOWS\system32 folder ?

#5 elinap

elinap
  • Members
  • 2 posts
  •  
    United Kingdom

Posted 29 July 2009 - 07:07 PM

@elinap

Strange difference ....

Can you try FIXPATH.exe
More Info: http://www.msfn.org/...o...112627&st=2


What do you get when you open cmd window and give VER and then [Enter] key ?

Are find.exe and findstr.exe present in C:\WINDOWS\system32 folder ?


1. where is fixpath.exe and what is it for?
2. ver 5.1.2600
3. yes, both of them are present

I managed to sort out the problem by running the program in another xp sp3 machine.

Thanks for the reply.

#6 zainka

zainka
  • Members
  • 1 posts
  •  
    Norway

Posted 31 October 2011 - 09:03 PM

Hi, I know this is an old topic but here is the solution for why you have the problem elinap reported.
i.e.






find: 6.0.: No such file or directory

FIND: Windows NT: No such file or directory

FIND: invalid predicate `'

Press any key to continue . . .

This is due to the PATH variable been updated by programs installed which does not follow the rules and add them self in the beginning of the path variable, pushing the systemroot variables (i.e. c:windowssystem32 and such) further bach into the path variable list. This will effectively make some programs fail.

I know this to be true for WinAVR which puts refferences to itself in the beginning of the PATH variable. WinAVR does this cause it comes with certain replacements to standard windows apps like for example find ....

So, if by running command 'echo %PATH%' in a command window does not show c:windowssystem32 in the first entries, you have troubles.

Another solution would be for usb_multiboot to search for the windows path in a more direct and hardcoded way.


Breg
Vidar

Edited by zainka, 31 October 2011 - 09:04 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users