13 replies to this topic

[doctortonic]

I am making a Multi Bood dvd with Xboot and in my project is also included ubcd4win ( ultimate boot cd for windows ) but,
unfortunatelyI have a blue screen of death (bsod) error.
The scenarios is this one:

I created the Ultimate Boot CD 4 Windows iso and It boot's with a real succes on the real hardware as well in the Virtual Machine (vmware, qemu, virualbox)

And When I add the ubcd4win iso image I have selected Grub4Dos





Now, the multi iso boot DVD has created, the iso dose make the boot, but when UBCD4WIN loads it gives a blue screen on virtual machine and on real hardware as well

The screen that I have before the blue error is this one:




Next step after this Screen I have this one with BSoD




How I can overcome / fix this problem?

The ubcd4win image it is okay/fine, it dose boot so grub4dos do the job, but when ubcd/windows/bartpe is loading I have that blue error. I am thinking that has something to do with " ISO in ISO ".
Dose anyone has any sugesstions?

Thank you in advance.

[steve6375]

Try hard disk emulation?

[doctortonic]

With Hardisk Emulation I have this error:







Edit 1: My guess is that the image it has to be somehow " un-iso-ed ", because I did have succes with ubcd4win and Sardu utility, which is
" extracting " the ubcd4win iso image before adding it to the final multi boot iso.

I know that I could use Sardu and add some tools with it, But I prefer Xboot for obvious reasons.

Edited by doctortonic, 15 March 2012 - 11:17 AM.

[steve6375]

You don't seem to have a menu.lst.
Maybe http://www.rmprepusb...orials/ubcd4win will help you to make a menu.
You can boot from ISO - see part 3.

[Wonko the Sane]

The 0x0000007b means that you miss a driver for the image.
A "standard" UBCD4WIN .iso CANNOT be booted with .iso mapping unless you either add inside it a suitable driver or use an external driver (using the "F6 floppy disk" feature).

You need EITHER of the 2003 SP1 ramdisk driver or another driver (Firadisk, Winvblock, Diskless Angel) - the Tutorial by Steve6375 uses Firadisk driver.

See here:
http://reboot.pro/8944/
and here:
http://reboot.pro/2692/page__st__26
to get the "general idea".

Find some specific info on the "old" 2003 SP1 approach in this seemingly unrelated thread:
http://reboot.pro/4952/.

I know that I could use Sardu and add some tools with it, But I prefer Xboot for obvious reasons.

I am unaware of such "obvious" reasons, would you mind listing/explaining them?

What happens if you choose in the menu the "Utility ---- PE, MSDART, ERD (Windows XP only)" option?
(UBCD4WIN is a PE and it is XP based)






Wonko

[doctortonic]

I am sorry for the looonnnnggg post but, thank you for patience reading it.


If I boot ONLY the UBCD4WIN .iso image work's.
If I add the ubcd4win image that work's to xboot, it dosen't work.

I have a menu.lst in the root of the image folder, here is the code:

color black/cyan yellow/cyan

default /default

default	 0

timeout	 10

title Launch "The Ultimate Boot CD for Windows"

fallback 1

find --set-root /ntldr

chainloader /ntldr

savedefault --wait=2

title commandline

savedefault --wait=2

commandline

title floppy (fd0)

chainloader (fd0)+1

rootnoverify (fd0)

savedefault --wait=2

title reboot

savedefault --wait=2

reboot

title Darik's Boot And Nuke v2.0 ~ Submenu

configfile /dban-Grub4dos.ini

title FreeDos

map --mem (hd0,0)//Images/freedos.img (fd0)

map --hook

chainloader (fd0)+1

rootnoverify (fd0)

title GOBACK Removal Tool

map --mem (hd0,0)//Images/goback.ima (fd0)

map --hook

chainloader (fd0)+1

rootnoverify (fd0)

title Memtest86+ v4.10

map --mem (hd0,0)//Images/memtestp.img (fd0)

map --hook

chainloader (fd0)+1

rootnoverify (fd0)

title NTFS-Dos

map --mem (hd0,0)//Images/ntfs4dos.img (fd0)

map --hook

chainloader (fd0)+1

And Here is how it look's when I boot ONLY the ubcd4win iso image:





As I said, Sardu is doing something to the iso because It takes a longer time and I have this screen when I am making the multidvd with it, so it is extracting something from ubcd4win before making the multiimage, not just copying the image to an iso.


__________________________________________________________________________________





The "standard" / "native" UBCD4WIN .iso DOSE boot, I did already a test in vmware player, qemu, on two laptops and at one pc/workstation.
All computers have different hardware, same platform.

I have problems only with the iso created by Xboot wich contains ubcd4win, all other utility's are working fine (hdd tools, linux, acronis etc.)

This iso is already having drivers in it.

__________________________________






When I try Utility ---- PE, MSDART, ERD (Windows XP only) I have this error:

ERROR REPORT ( 03/07/2012 17:53:11 )

Please submit this error report to developer.

Operating System version  :Microsoft Windows NT 5.1.2600 Service Pack 3

.NET Framework version	:4.0.30319.1

Error Message			:

Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.

StackTrace			   :

   at A.V.D()

   at A.V.D(ImageItemBase , Exception )

   at A.KB.D()

   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ThreadHelper.ThreadStart()



ERROR REPORT ( 03/15/2012 13:31:40 )

Please submit this error report to developer.

Operating System version  :Microsoft Windows NT 5.1.2600 Service Pack 3

.NET Framework version	:4.0.30319.1

Error Message			:

Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.

StackTrace			   :

   at A.V.D()

   at A.V.D(ImageItemBase , ProcessLog )

   at A.FB.D()

   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ThreadHelper.ThreadStart()



ERROR REPORT ( 03/15/2012 14:11:07 )

Please submit this error report to developer.

Operating System version  :Microsoft Windows NT 5.1.2600 Service Pack 3

.NET Framework version	:4.0.30319.1

Error Message			:

Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.

StackTrace			   :

   at A.V.D()

   at A.V.D(ImageItemBase , ProcessLog )

   at A.FB.D()

   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ThreadHelper.ThreadStart()

___________________________________________________

Why xboot over sardu should be another topic.

1) Xboot has a nicer and more estetic background on the boot menu (sadly it can not be changed, or there is some way and I don't know it)
2) Xboot give me the posibility to make my own menu and this is important,

Like:

Category:

Tools for hdd
Tools for backup
Linux related iso's

And it's very nice because I can choose the order in wich the iso's are arranged in the menu, eg. the first iso wich you will add will be the first iso in that menu.

It dose NOT restrict / limit me on what distro / iso I can add as Sardu
It worked with every iso wich I tested

...​with the exception of ubcd4win in this particular case.

It has a qemu built in and that's SUPER DUPER, just drag&drop!

[Wonko the Sane]

I see that you completely failed to read the given links.

The 0x0000007b means that the driver to access the .iso is missing.

If I boot ONLY the UBCD4WIN .iso image work's.

HOW EXACTLY do you boot successfully the .iso image "on it's own"? (Which loader, which settings, which menu.lst or .cfg entries?)


The fact that you tested the .iso in a VM (mapping it as CD in it) or on a real CD on real hardware has nothing to do with having it boot from .iso file (mapping the .iso file as virtual CD device in grub4dos or similar).

You can stamp your feet all the time you want, but until you will add - one way or the other - a suitable driver, that .iso won't boot.

If you actually had read the given links by Steve6375 and myself, you should have already:

• understood what the underlying issue is
• have two possible solutions to the problem

You don't really need to use bold, BIG FONTS or COLOURS, most of us have an average eyesight and can read normal text.

The two reasons, are not really-really "obvious":

1) Xboot has a nicer and more estetic background on the boot menu (sadly it can not be changed, or there is some way and I don't know it)
2) Xboot give me the posibility to make my own menu and this is important,

As you can change the "background" of the boot menu easily (once you learn how to) and as well you can change menus on the "results" of BOTH Xboot and Sardu.
Both are simply "helpers" that use the functionalities of third party tools (Syslinux/Isolinux/Memdisk and grub4dos) and a number of known "pre-sets" for a number of distro's/OS's.
Everything they do can be done (or re-done or corrected or "tuned") "manually".


Wonko

[steve6375]

What happens if you try the Utility - PE Vista/7 option for Xboot?

[doctortonic]

It seem that this problem is overwhelming me by it's complexity because I can't figure out how to solve it.

I am so sorry that I did not make a school in the IT domain.
I would like to be better educated to all what involves computers, or to have a job in the computers field.

I didn't know that changing size && font && colors is disturbing for you guys, I just thought that is better readable this way.

Please accept my humble apologies.

I did took a quick look at the links, and now once again but this time longer trying to digest the information but I will need more and more time to really understand what is "under the hood",
and being just a personal project for getting rid of so many cd/dvd I have I think I will quit it and leave ubcd4win on another dvd.

I am working at this project from over a week now, reading documentation and testing things, trying to figure out how ubcd4win work, finding other software, reading about linux distros etc. and I think it is time to move on and leave it as it is.

Maybe in the future problems like this will be surpassed.

I do understand that this tool is in beta/testing stage and it is not final, and so I have no big expectations from it.

______________________________




If I try Utility - PE Vista/7 option it has this symptom:

ERROR REPORT ( 03/07/2012 17:53:11 )

Please submit this error report to developer.

Operating System version  :Microsoft Windows NT 5.1.2600 Service Pack 3

.NET Framework version	:4.0.30319.1

Error Message			:

Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.

StackTrace			   :

   at A.V.D()

   at A.V.D(ImageItemBase , Exception )

   at A.KB.D()

   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ThreadHelper.ThreadStart()



ERROR REPORT ( 03/15/2012 13:31:40 )

Please submit this error report to developer.

Operating System version  :Microsoft Windows NT 5.1.2600 Service Pack 3

.NET Framework version	:4.0.30319.1

Error Message			:

Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.

StackTrace			   :

   at A.V.D()

   at A.V.D(ImageItemBase , ProcessLog )

   at A.FB.D()

   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ThreadHelper.ThreadStart()



ERROR REPORT ( 03/15/2012 14:11:07 )

Please submit this error report to developer.

Operating System version  :Microsoft Windows NT 5.1.2600 Service Pack 3

.NET Framework version	:4.0.30319.1

Error Message			:

Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.

StackTrace			   :

   at A.V.D()

   at A.V.D(ImageItemBase , ProcessLog )

   at A.FB.D()

   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ThreadHelper.ThreadStart()



ERROR REPORT ( 03/15/2012 14:46:45 )

Please submit this error report to developer.

Operating System version  :Microsoft Windows NT 5.1.2600 Service Pack 3

.NET Framework version	:4.0.30319.1

Error Message			:

Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.

StackTrace			   :

   at A.V.D()

   at A.V.D(ImageItemBase , ProcessLog )

   at A.FB.D()

   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ThreadHelper.ThreadStart()



ERROR REPORT ( 03/15/2012 16:42:47 )

Please submit this error report to developer.

Operating System version  :Microsoft Windows NT 5.1.2600 Service Pack 3

.NET Framework version	:4.0.30319.1

Error Message			:

Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.

StackTrace			   :

   at A.V.D()

   at A.V.D(ImageItemBase , ProcessLog )

   at A.FB.D()

   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ThreadHelper.ThreadStart()

________________________

P.s. How can be changed the wallpaper / background image and text colors & size?

[Wonko the Sane]

It seem that this problem is overwhelming me by it's complexity because I can't figure out how to solve it.

I am so sorry that I did not make a school in the IT domain.
I would like to be better educated to all what involves computers, or to have a job in the computers field.

All you have to do is to follow EXACTLY the steps in point #3 of the Tutorial by Steve6375 (and of course feel free to ask questions about the specific steps that you fail to understand)

The general idea is that when the "protected mode" part of the booting "kicks in", a driver must be found to "hook" the image mapped by the "real mode" part of the booting, in the case of NT (2K/XP/2003) the system is re-scanned by NTDETECT.COM and if no driver "hooks" the image, you get a 0x0000007b.

I didn't know that changing size && font && colors is disturbing for you guys, I just thought that is better readable this way.

Please accept my humble apologies.

No prob whatsoever .

I did took a quick look at the links, and now once again but this time longer trying to digest the information but I will need more and more time to really understand what is "under the hood",
and being just a personal project for getting rid of so many cd/dvd I have I think I will quit it and leave ubcd4win on another dvd.

I am working at this project from over a week now, reading documentation and testing things, trying to figure out how ubcd4win work, finding other software, reading about linux distros etc. and I think it is time to move on and leave it as it is.

Oww, comeon.... giving up is NOT an option!
Go doctortonic, go!

I do understand that this tool is in beta/testing stage and it is not final, and so I have no big expectations from it.

Actually judging from the fact that shamurshamur is seemingly MIA since Jul 23 2011, it seems more like an "abandoned" beta.


Wonko

[cdob]

Could not load file or assembly 'PGK.Extensions

Add file PGK.Extensions.dll
http://reboot.pro/15...post__p__143778

[doctortonic]

PGK.Extensions.dll Solved half of the problem,

With the

Utility -- PE MSDART ERD ( XP ) I had that black screen grub error

and with

Utility -- PE MSDART ERD (Vista & 7 only) I had the blue screen 0x0000007B
_______________________________________________________________



If I follow Steve tutorial http://www.rmprepusb...orials/ubcd4win Step3 will be a workaround but
It will not work on older systems. (ex. a Pentium III and 256 Mb of ram)

Note: Regardless of if you use an .iso file or a .gz file, because the whole contents of the iso file is loaded into and runs from memory (RAM); you will still need a system with 1GB of memory (or more) and the amount of free memory once UBCD4Win has booted will be reduced by the same size as the files (i.e. 600+MB of files), so on a 1GB RAM system you may only have 200MB of RAM once UBCD4Win has booted.

I wonder how can I edit the files which resides in my xboot.iso image not into a usb stick,

like menu.ls from root of the iso image

or change/replace bootsyslinux.xboot.jpg

But before that I am thinking to inject/replace somehow directly into the final iso the modified ntdetect.com from step 2.


Beside Stamping My Feet here ,

I feel love from Donna Summer

Is a good song.


Right now while writing this I am thinking which could be the magic that Sardu is doing to the ubcd4win, what approach it takes, I am thinking that maybe the instructions from the menu.lst from sardu image can be merged into the menu.lst created by xboot. Hmz,
back to reading doc's and tutorials

Edited by doctortonic, 15 March 2012 - 06:28 PM.

[steve6375]

Sardu is extracting the iso to make a flat file installation. You can do this too (first part of the tutorial) and then you won't need a lot of ram. However this limits you to one ntldr/xp/winpe v1 flat file per USB drive unless you modify the boot.ini to multi-boot and have multiple partitions.

[Wonko the Sane]

@steve6375
Actually it is perfectly possible to have several "flat" PE 1.x's, as long as we can modify the SETUPLDR.BIN.
http://www.msfn.org/...le-pe-from-usb/

(and the interesting part would be doing so on a NTFS formatted stick partition and hard-link same files )



Wonko