Jump to content











Photo

My error Log


  • Please log in to reply
1 reply to this topic

#1 anonymous10

anonymous10

    Newbie

  • Members
  • 25 posts
  •  
    United States

Posted 02 January 2017 - 01:06 AM

Hello reboot!

Thanks for you help last time. I have a new problem. So I was able to reboot Gandalfs PE. However it had limited capability and no internet, which I have never seen before. When I boot with rufus, it works perfectly, but I want to use xboot, so I can put multiple tools on one USB. I bought a 32 GB flash drive for this purpose.

This is what the error log showed from the limited capability PE. I was wondering what advice you can give me or what adjustments I can make to get this fully functional. I felt this was the appropriate place to post this since I think its a problem with xboot, or the settings I am choosing.

CdUSB.Y or ISO NOT found !
Win10PESE can not mount and access files of your CD/DVD, USB, ISO on drive Y:

Possible Reason and Solutions :
1) You are using UFD (USB Flash Disk) as boot media formatted in NTFS.
---> Use FAT32 with UFD :>    ( Format UFD with FAT32).

2) You are not using .iso boot (You are using RealCD/DVD, BCD BOOTMGR, grub4dos BOOTMGR, etc.).
---> Check that the flag file CdUsb.Y is at the root of your media.
---> Your drive remained to the state "Not Ready" (More than 30 seconds) for a hardware reason.
---> Your drive is not recognised (driver missing or whatever, check if you can see your CD or Usb drive letter on explorer).

3) You are using .iso boot (grub4dos, isolinux, etc.) but you changed the build .iso name or path of your iso (ex: Win10PE_x86.iso, \Images\Win10PE_x64.ISO).

* If you use all from ram (all inside .wim) ignore this warning ;).
+ If you need files in your .iso to access, read following.

A) This feature requires imdisk, else will not work.
---> Be sure you have imdisk on your Win10PESE (Enable at Win10PESE\Tweaks).

B) Change your .iso name to the build .iso name (ex: Win10PE_x86.iso ) and put it to the correct path of your bootdrive.
---> Look for the default build configuration in the internal ini file (X:\Windows\System32\MountPEmedia.ini section IsoInfo/IsoName).
---> Rebuild by giving your personal Iso file name\Subfolder in the plugin Finals\Create ISO.

C) Use Win10PESE.ini to specify your personal .iso file name and location (solution for without rebuilding your project with your custom .isoname/subfolder settings).

3b) You are using .iso boot (grub4dos, isolinux, etc.) but .iso file to mount not accessible.
(= you can not see your Win10PESE iso file with explorer).
---> Driver missing -> add driver for your disk.
---> Some windows settings or software which disables mounting drives at boot -> disable such setting/software.
---------------------------------------------------------------------------------------------------------------
9) Contact http://spam
----------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------

MountPEmedia.exe : Mount files of your CD/DVD, USB, ISO on drive Y:

Ini File (MountPEmedia.ini) :
  [Settings]
  ProjectName=Win10PESE
  MountDrive=Y:
  SearchFlagFile=Yes
  FlagFileName=CdUSB.Y
  SearchExternalIniFile=Yes
  ExternalIniFileName=Win10PESE.ini
  DesktopWarningLabel=Win10PESE Warning

  [IsoInfo]
  IsoName=Win10PE_x86.ISO

Program Imdisk found in : X:\windows\system32

=====>   Passage : 1
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 2
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 3
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 4
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 5
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 6
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 7
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 8
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 9
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 10
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 11
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 12
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 13
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 14
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 15
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 16
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 17
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 18
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 19
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 20
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 21
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 22
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 23
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 24
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 25
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 26
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 27
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 28
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 29
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

=====>   Passage : 30
DRIVEGETDRIVE(ALL)
Drive C: - READY - Windows
Drive D: - READY - RECOVERY
Drive E: - READY - XBOOT

All drives are ready but without finding CdUSB.Y or the ISO file in the allotted time of 30 seconds ! Exit.



#2 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13408 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 02 January 2017 - 11:41 AM

XBOOT is not anymore developed, it starts to show its age and - to be frank - never was such a "good" tool.

 

It is very likely that you will encounter every kind of error (+1) when using it with anything later than around 2010, in any case it is UNsupported because the developer sadly died in an accident and the source was never released.

 

There are several other multi-boot tools around, among them one of the most flexible and actively supported is Easy2Boot:

http://reboot.pro/to...ent-discussion/

 

In a nutshell, if you insist on wanting to use XBOOT, you are essentially on your own, while more recent and actively mantained tools will probably work fine and even if they should not work you will find support and assistance to solve those errors.

 

Finally XBOOT is essentially a wrap around either Syslinux or grub4dos functionalities (both in obsolete versions) just like Easy2boot which is mainly an automated system around the features of - mainly - grub4dos, so if you want actual control you should learn how to use grub4dos directly.

 

:duff:

Wonko






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users