NOTE: I consider the following method outdated. There are currently better methods included with UBCD4Win and I recommend using pcuser's UBUSB.exe instead. It automates the steps below and includes a Kicker CD option which is great for computers that can't boot directly from USB. I'm no longer providing the zip file with the files needed for the below steps. If for some reason you need those files, send me a message. Thank you.
-----------------------------------------------------------------------

When I first started using UBCD4Win I set out to see if I could have a fully functioning version boot from my flash drive as I always carry it with me. At first I was able to get just the UBCD4Win environment to load, but was then able to have a functioning Windows Recovery Environment and boot menu. I thought I would share the steps I took to do this.

To get started we need to download some files:

1. Download PeToUSB from GoCoding.com and extract it to C:\temp\PeToUSB.
2. Download Syslinux from Kernel.org and extract it to C:\temp\syslinux.
3. Download the zip containing the boot menu files from my website and save it for later.
4. Build UBCD4WIN as you normally would. If you plan on using the windows recovery console make sure Multiboot is turned on and the recovery console option is enabled.

Now the fun part:

1. Run PeToUSB.exe from C:\temp\PeToUSB. Make sure your flash drive is selected in the drive selection list. If your drives are not showing up in the list, make sure you are logged in as an administrator. [dougham - 11/28/07] I would recommend to enable disk format and to select Enable LBA. I had some issues with Dell computers that were solved when I turned this on. This was causing a 0x007 BSOD. If you still receive this BSOD, try using the NTDETECT.COM, SETUPLDR.BIN, and RAMDISK.SY_ that are found on the Windows Server 2003 CD. [masterchi - 11/28/07] Enable file copy which will copy all of your UBCD4Win build files and the correct ntldr and NTDETECT files over. Press "Start" and let it run.
2. Open a command prompt and change directory to C:\temp\syslinux\win32. Type “syslinux [your flash drive's letter]”. My flash drive was F so I typed:
   CODE
   syslinux F:
   If you don't see any errors you should be good to go.
3. If you are going to be using the Windows Recovery Console make sure you have a CMDC directory in the root of your flash drive. If it’s not there, copy it over now (from your UBCD4WIN build directory) as the zip file in the next step will overwrite setupldr.bin with a modified version.
4. Extract the zip file you downloaded from my site to the root of your flash drive.
5. Delete the following files/folders from your flash drive’s root if they exist:
   
   1. BCDW
   2. isolinux
   3. images
   4. Etc
   5. BOOTSECT.BIN
   6. Win51IP.SP2
   7. Win51IP
6. Delete the temp directory your created in in step 1. It might be handy to keep PeToUSB and my .zip file around.

You are done! If you need to add or remove programs from the boot menu, you will need to edit syslinux.cfg in the syslinux folder (it may be hidden). The disk images for the programs are stored in the /syslinux/images directory. [masterchi - 11/28/07]
If you have any issues or questions please let me know. I hope this can be useful to people and help save all the time and research it took me to figure this out.

Last updated: 03/08/09

This is a very popular topic and our users will appreciate the time you spent writing this guide.
I'm going to pin this topic so it stays at the top of the list.

THANX

@ALL
Can anyone confirm this method does work?
Please post the hardware you are testing with as each method seems to depend at least slightly on system configuration.

Hilander999,

Thank you so much for doing that. I had a tough time and had not seen any one integrate the boot menu. I hope this will save every one some time and effort. If any one has any issues please let me know and i'll help you the best that I can. Also if any one would like to make this a plugin (if that can be done), please contact me and i'd be happy to help with that.

No problem, as I said this question has been asked A LOT.

You should "Subscribe to this thread" so you will recieve an email any time a new post is added.
That is the best wat to track what needs to be done to make it universal.

Part of this can be done in a plugin, the rest needs to be scripted & we will soon have some new scripting features built into the endbuild process.
It will be neat to see how the project matures from here out.

THANX AGAIN, and keep us updated on any changes you find neccessary.

So this method includes the initial blue background boot menu where you can choose MemTEST or any other custom made images instead of just booting to UBCD4Win? Awesome, I'm going to give it a shot here at work when I have a chance. I've had nothing but good luck with my method of USB booting but it never included the boot menu. I'll post here later today on how it goes.

@masterchi
Start a new thread for your method, which I know is already posted in another thread somewhere.... & let's git it pinned here also.
We are looking at alternatives for the boot menu, so give us a good opinion of how this one works for you.

Mention here that you should copy over the files not extract it or else it will overwrite the CMDC folder with the one on your zip that has nothing more then a SETUPLDR.DIN file. I simply copied the file over to the CMDC folder on the Flash Drive and replaced it.


Might be worth mentioning that you also have to copy over your images to the syslinux\images folder on the Flash Drive once you make the changes.



From what i noticed so far i am unable to get ISO's to boot though when i edited the SYSLINUX.CFG file i copied the same structure but i made the KERNEL memdisk for the ISO images but i am not sure if that is wrong, i can check the syslinux website but maybe one of you know how to boot ISO files in syslinux.

List of my results on a Dell GX260 computer (i will try other models later):
The Windows Recovery Console came up with a 0x007b BSOD.
Offline Password and registry editor boots just fine.
NTFS4DOS does not boot, it just sits at "Starting....."
GOBACK boots up but i don't have any goback machines to test it on so i assume it works.
DBAN Booted just fine.
UBCD4Win i recieve a 0x007b BSOD

I am going to try to replace all instances of NTDETECT.COM, SETUPLDR.BIN, and RAMDISK.SY_ that are found on the thumbdrive with the same files from a Server 2003 CD to stop the BSOD. On my method of UBCD4Win booting on a thumbdrive i had to do this so i will give it a shot and post back on what happens.

One Question to DummptyHummpty.......Is the SETUPLDR.BIN file in CMDC specially edited? I am going to replace that file with a server2003 SETUPLDR.BIN unless you tell me otherwise. I like the option of having the bootmenu though we need to work out these issues. I might not have time today to make these changes but i will give it a shot and post back either today or tomorrow whenever i find time.

Nice Job though DummptyHummpty, i like it so far

All right I have subscribed. I'll keep an eye out for that scripting and then maybe start working on a plugin.



Well, the menu looks a little different and the background is actually the UBCD4Win logo, but yes it's the menu with all the programs like Memtest, DBAN, Recovery Console, etc. If any one has suggestions on tweaking the layout, please let me know!

Ok after i replaced all instances of NTDETECT.COM, SETUPLDR.BIN, and RAMDISK.SY_ that are found on the thumbdrive with the same files from a Server 2003 CD i was successfully able to boot to UBCD4Win and the Recovery Console (no more 0x007b BSOD). NTFS4DOS still does not work

I am still having trouble with ISO images though and didn't find much help on Syslinux on whether they allow booting to ISO images or how to make them work. An excerpt from the changes i made on my current SYSLINUX.CFG file looks like this if anyone can help(and yes i copied the images to the correct path in the SYSLINUX folder so that is not an issue):




As you can see i bolded what i think could be the issue but i followed exactly how these were written for IMA and IMG files with the KERNEL entries and as you can tell i made sure the capital letters are exactly like they are on the working entries. Any info on ISO images in SYSlinux would be great. Thanks.

**EDIT**I haven't looked at fixing it yet but it would be best to change the font color on the boot menu to black if possible, the white font on the UBCD4Win background makes it a bit hard to read.**

It should have just overwritten SETUPLDR.BIN, not the whole directory. What program did you use to extract the .zip? What method did you use for that program?


Ok i'll add that in.


I don't think you can get SYSLINUX to boot ISOs. What I did was open the .iso files in WinRAR. There was usually a .img or .ima file and that is what I had syslinux use. You may get lucky and find that the .iso is using ISOLINUX. Just find the ISOLINUX.CFG file and copy the parameters to your SYSLINUX.CFG file.


This is the problem I had with the Dell computers and enabling LBA seemed to help this. However, I did encounter one computer that still would not boot. The SETUPLDR.BIN is specially edited. Unedited, it would see the MININT directory and boot from that instead of the CMDC (recovery console directory). I used a hex editor and replaced all references to MININT with CMDC and then hexed in "00" for each of the remaining spaces fom "N" and "T". Can you confirm that your recovery console loads correctly with your replaced SETUPLDR.BIN?

Also I was not able to get NTFS4DOS to work here and was not sure if it was specific to my machine. It looks like it was not. I'll note that in the first post. Does any one know what might be causing it to stall at "Starting..."?

Thank you, I hope you find this useful and please let me know of any other issues you encounter.


See my note above about using ISOs. I'll play around with the menu in a bit and see if I can change the font to black.

Yes it does work correctly. It loaded up and i hit R for recovery and it saw both partitions, My C: drive on the local computer and the MININT directory on my jumpdrive but i was able to successfully select 1 (for C:\Windows) and i ran CHKDSK \R without issue.

Also i did follow your steps exactly and i did check the box "ENABLE LBA" but that didn't stop the BSOD's from happening so ?? But its working now so it's ok. I will check on ISOLinux to possibly create something similar but it will be able to boot ISO's in the boot menu but from what i read it seems ISOLinux does have issues with certain BIOS's that SYSLINUX is not hindered by so syslinux is the best choice.

I'll see if i can make some changes and convert those ISO's to IMG files, i'm sure i can make the Spinrite into a IMG and MEMTEST86+ but the Drive Fitness Test DFT might be a bit more difficult :S

I'll update if i have more news.

That's very odd that it works. I'm going to PM you my e-mail address, would you mind sending me that file so I can take a look at it?


All right, I was just checking. It's good to know that using the Server 2003 files is another solution to the problem. Maybe i'll make a FAQ section and put that in.



I didn't mean for you to convert the .iso files themselves and I didn't mean for you to use ISOLINUX instead of SYSLINUX. If you open the .iso files up in WinRAR or WinISO you can see the directory structures. Alot of times you will see an ISOLINUX directory that loads an .img or .ima file. These files can be loaded by SYSLINUX, so you want to extract them (either the .img or .ima) and have SYSLINUX load them. If your not sure of what commands to use in SYSLINUX.CFG, see if the .iso has a ISOLINUX.CFG file where you can copy the commands from. Let me know if I can clarify further. If I have time, i'll try and get you the correct files for Memtest86+ and DFT.

For what it's worth, UBCD4DOS 4.1.1 uses syslinux and it includes memtest86 3.3, memtest86+ 1.70, and Drive Fitness Test V4.09 (IBM/Hitachi). If you don't want to include all of the UBCD4DOS tools on your flash drive, you can pick and choose what you want. If you enable the option for UBCD in UBCD4WinBuilder's plugins, it will download it and extract UBCD4DOS's ISO contents to plugin\Multiboot-003\ubcd\files. The files you want for those three are boot\memtest, boot\memtestp, and images\dft.igz.

As for Spinrite, I've found that it makes a difference for its speed as to what DOS environment you run it from. UBCD4DOS gives you several options for your DOS environment, and the one I settled on was LZ-DOS. To use it, you also need to copy over /images/lzubcd.igz, and you need to place spinrite.exe either in the root folder (with no startup.bat file), or in a sub folder "dosapps\spinrite\" with a startup.bat file also in that folder. I did the latter so that I could pass the dynastat 1 command line parameter to it, since I hate how long it takes to deal with bad sectors otherwise.

After looking through all of the menus, I don't see anything that looks like an ISO. It looks to me like the UBCD4DOS folks converted all the tools to not use ISO images.

Here's some menu items you can use for those 4 things, which I'm basically just copying/pasting from my UBCD4DOS menu structures. I haven't actually tested this stuff with a flash drive yet, but they work fine from CD:



Oh, the ^ in the Spinrite label makes it so you can just type the letter S and it jumps to that menu entry. Also, if you put the memtest and memtestp files in \images instead of \boot, be sure to change the lines to point to /images instead.

And just in case anybody reading this thread doesn't know how to make a startup.bat file, here's what I threw together for the one I included in my Spinrite sub-folder:

Xibur,

Your on the right track. That's basically what I was saying to do. If anyone thinks I should includes these in my .zip let me know.

@XIBUR

Thanks that helped a lot. I have the two MEMTEST's and DFT working now (i didn't know they were on 4.09, i was still using 4.08) Thanks. Unfortunately Spinrite.iso is still not working for me. I copied and pasted exactly what you had and copied the files over from the UBCD4DOS CD and it loads through DOS just fine then sits at a prompt Q: and i typed DIR and saw nothing for startup.bat or spinrite so i went C: and went to the C drive (my USB) and i typed in spinrite.iso and even startup.bat and it didn't work, just an error that it is an unknown command.

I might not of fully understood your description for spinrite so correct me if so:

I edited SYSLINUX.CFG to be like this


and then i copied of the LZUBCD.IGZ file and created the bat file as you mentioned by copy pasting what you had and changing the path in the batch from the DOSAPPS to where the ISO is located for me and just get unknown command SpinRite. Any ideas if i did this wrong? If not i think i still have the executable so i can have it create a floppy image instead of a CD image. Thanks.

You need to be using Spinrite.exe directly, not Spinrite.iso and not a floppy image, though a floppy image might be usable with a different menu entry. And you need to put that exe in 1 of 2 possible places that I'm aware of for it to be automatically launched in this way, either the root folder or in the \dosapps\spinrite\ sub-folder. In other words, when you use the ubcdcmd=spinrite command (note the lack of an extension on the end), the LZ-DOS image that the UBCD4DOS guys specially crafted is going to look for \spinrite.exe or \dosapps\spinrite\startup.bat.

I was just trying to find where the ubcdcmd=<command> is documented but couldn't find it. I think maybe I studied the autoexec.bat file from inside the lzubd.igz image file or something in order to figure that out. Sorry I can't point you to better documentation at the moment.

The main reason I did it this way is that I was adding it to a boot disc where I had all the UBCD4DOS tools included, and just adding the exe was the smallest method. But I suppose if you're not using all the tools, a floppy image of Spinrite might be the smallest method. In that scenario, you can exclude lzubcd.igz, make a floppy image of Spinrite, maybe compress it using 7-Zip and the gzip method, rename the compressed floppy image file to spinrite.igz, and use a menu entry something like this instead:



Just to be clear, here's a menu entry you can use for the UBCD4DOS method that better reflects your changes:



I haven't tested the floppy method, but if it works right, you now have the choice of two different methods. And actually, there's no reason (other than space considerations) you can't use both at the same time, if you wanted to see which one you prefer. If you want to use both, you just have to be sure they each have unique LABEL (and MENU LABEL) entries, which are modified for you above, and that you include the appropriate files of course.

And just to further clarify the overall idea here, syslinux appears to not like ISO image files. At least, nobody has figured out how to make ISO image files work with it directly and has cared to demonstrate it, yet, that I'm aware of.

@Xibur

Ahh, use the EXE. It makes sense now I will try it tomorrow but as i mentioned before it loads the LZDOS but then just sits me at a Q: prompt for me to enter commands but with your method it should run startup.bat automatically as long as it see's it? I guess i was expecting an error about "cannot find file" or a "unknown command" if it was running it automatically.

Also, i'm not sure if using my EXE will work. When i double click my EXE in windows it brings up the menu where i can create an image, create a boot disc, or install it on local drive. There is no option to run it so i am skeptical if it will work correctly but i'll give it a try tomorrow and post back. Thanks.

I used the SETUPLDR.BIN file you e-mailed me and your correct, it boots the Recovery Console correctly. I have not compared them with a hexeditor, but they must be different. I'll have to figure out if we should start using this file or use the one I edited. It's probably best to use the non-edited one.

Thanks to the OP worked first time for me; pulled the files from server 2003
http://pcf.mundayweb.com/index.php?view=17...3c3449702d3e96a

After all these years I FINALLY have a bootable thumbdrive!! Well in the past I never really found the time to do it and honestly didn't have much desire for one. I've been content with booting from CD's, however users have always asked me/us how to do this. Since your instructions looked pretty easy I figured we finally had some easy to use instructions for users. I of course like to go through the process a few times that way if I make mistakes I can help answer user questions when they make a mistake.

The method has inspired a few of us to do a little more for USB booting. We're working on a few things so hopefully we'll be able to make it a little easier for users in a future release of UBCD4Win. Thanks for your help!

Hi all,

First, thanks alot for your very nice help.
I followed your instructions above, and i can get it to boot when i select the "The Ultimate Boot CD for Windows" and i had the error:

"cant find the file" when it try to load the Jushua's Pre-config
is there a way to not to load the pre-config ?

i dont know how to fix this, pls help
thanks

Need to test that! I test only this:
http://www.ubcd4win.com/forum/index.php?showtopic=9668

and that works!

Joshua

thanks alot Joshua, i will try that, i ve been spending alot of hours doing this and i enjoy doing it
your help always save us alot of time,
cheers
Tony-Syeney

I can't reproduce this error !
Can you do a test with this DEBUG PreLogon Version and post the results ?
http://www.drowaelder.de/winpe/ubcd4win/Jo...UG/PreLogon.exe

Joshua

In my testing I actually ran into this problem, however forgot to post what I think caused it and a few other comments.

That error message happened to me on my first build. I think I fixed it by changing some information in an XML file. Or it could have been caused by Vista Ultimate 64? I can't be sure of that because for the rest of my builds I did them in an XP Pro Virtual Machine.

My second build- worked but the menu was messed up. This was a simple newbie mistake, something that I didn't really think about until I had problems. After a little while my brain started working and I remembered some past discussions. In UBCD4Win builder I had elected to NOT build the ISO, big mistake. Mistake because then post processing is not completed because AutoBuild isn't run!! So you basically have to tell UBCD4Win builder to make the ISO, but then disable the "AutoBuild 95: Build ISO" plugin.

My third build- was my successful one!!


Now to fix the problem. Navigate to "C:\UBCD4Win\OEM1\nu2menu". Open the nu2menu.xml file to edit it. Do a search and replace, you need to search for:

and replace it with:

There should only be one instance of this to change. Save it and then build again, I hope it works for you!!

Not that important, but if you add the below to the autorun.inf
it will show up in the AutoRun menu when the USB-flash is inserted

[autorun]
open=Programs\nu2menu\nu2menu.exe
icon=Programs\nu2menu\nu2menu.ico
action=Run the nu2menu Program

extract icons with BatchIconExtractor.exe

Thank you all for your kind response, i am testing it right now and let you know if it is ok

I was also running into the same problem.

I noticed you had a problem running under Vista. Could that be the problem? The iso created works fine but I can't boot from USB.

I am using a SanDisk Cruzer 2 Gb on a Gateway with a Phoeinx bios. U3 uninstalled. Followed directions without any errors.

I followed your instructions for editing the xml file but I am still getting the same error message.

Boot is recognized.
Setup inspects hardware.
Now loading...
Windows XP Splash Screen.
Blue Background with working mouse pointer.
Prelogn error. File not Found. Yellow Triangle with Exclamation Mark

Thanks for your help and hard work. It it appreciated.

===UPDATE===
I have the same problem when I use the other method that is pinned at the top of the forum.
So not an issue with your method. Maybe my build?

Did I see someone mention VISTA?

Please make sure you have disabled WINDOWS DEFENDER because it corrupts the driver files and causes all sorts of errors concerning the SHA HASH of the setup files.

i am using Vista Home Premium

I'm glad I could help you out. Let me know if you need anything. Also how come this thread isn't sticked anymore?



That's interesting. I'll have to look into this when I get to work. I remember changing something for nu2menu.xml, but I know I was able to boot before hand.



Hey that's cool. I can add that to the zip when I get into work tomorrow.

For a few minutes, i got the USB-stick files from dougham , who has the same problems.
I installed them on my working usb-stick, and now i got the same error!
On a quick view, the problem is in folder: \minint\SYSTEM32\CONFIG
it looks:


a normal looks:


I think it is a f*****g Marvelous vista, or antivirus problem !?
Well look later to that, it is time to go to bed !
03:15 AM here in germany !!!


Joshua

Hi Joshua,

Thanks alot for your finding, i will try it again, for the last few days, i tried but have no success,
i will try to edit \minint\SYSTEM32\CONFIG

as you said below and let you know

once again, thanks alot for your help as always

cheers
Tony-Sydney

Thats not what he meant.

your \config folder should not look like that so you have a problem with some sort of antivirus\malware software or perhaps even windows defender causing a problem.

You may want to go to MS and download the VHD IMAGE of Windows 2003 r2 and build in a virtual machine.

Joshua

Hi all,

I have success this time!

very happy

I had to use XP PC to build it, Vista is the problem!

I am writing to you using Bartpe on USB right now!
happy to get it work, thanks alot for your help
i will now test some other method

by the way, do you know why i have alot of entries for :"Apllication" or "Anti-Spyware tools" in the programs folder ?

thank you all
i have spent alot of time to get my wireless 3945abg work on this USB, and now it is working perfectly now.!!!
cheers
Tony

You must check the box to "Build ISO" or "Autobuild" will not run and this is where the menu and other items get cleaned up.
If you do not need the ISO there is an optional plugin you can disable, [Autobuild]Build ISO (or something very simular).

Hi, I just thought I would mention that this worked for me, although not thoroughly tested
and I'm posting from my USB PQI stick. I suppose I got a false positive from ipscan and
Symantec anti-virus 10. Well, time to go shopping, will write more later after testing. Stephen

These instructions worked perfectly for me right out of the box. I agree that the boot menu should have more contrast and I
thought that the wording for 'setupldr.bin' should be along the lines of 'extract setupldr.bin from the CMDC directory of the zip
file you downloaded from my website and copy it over the existing setupldr.bin found in the CMDC directory on the Usb stick'.
The extract did overwrite setupldr.bin but I also had two CMDC directories on my Usb stick. This is a splendid recovery tool
because sometimes I encounter computers with broken cd drives. I am still playing with this. I haven't got networking to work
because it wants to restart the computer. CMDC is a huge plus and I couldn't find that on the German version of Win XP USB
(60mb) which works but has almost no tools. I doubt that either the XP or Vista German USB boot version is legal. I had some
failures with other Google published methods even that involved Bart. How this works is so interesting. I have a computer with
two drives, Vista and XP, which I dual boot with 3rd party and it hides a partition to dual boot. I will test on that also. My system
for this build is fairly old, 1gig cpu, 512mb, and I think this must have been one of the first early bios which supported Usb boots.
Also I _think_ that only \I386 is used for building this, so why copy the whole XP installation cd content to the hard drive? I used
a good XP/SP2 disk and had zero failures or warnings. I wound up not minding the double and triple checking for file integrity.

PQI regards,
TechTonics

I am posting from the dual boot system which has a different MB. UBCD4Win took about
4 minutes to load, much slower than my other system which is half as capable. Maybe it
inspects the larger hard drives (s) on this computer? A43 did not show the content of the
Vista drive because of no drive letter assigned (only option delete).
I fixed that dell.inf problem for SR console by copying those 4 *.sys files into F:\CMDC
which is a less than elegant solution (which I later read about).

I'm glad to see that every one has been having success with my instructions. I'm sorry I had finals two weeks ago and was just busy with work last week. So what can I do to improve this, or is everything good. I'm still working on the menu, but i'm having trouble figuring out how to change it. Does any one know? Well i'll be back in the office on Wednesday and can do whatever needs to be done. Happy holidays to those that are celebrating them.

Joshua

Followed the instructions and it worked like a charm.

UBCD4WIN built upon XP SP2

$7.99 1G USB Flash stick from Micro-Center

These instructions.

Worked first time..... Priceless.......

Bonus: Windows Wireless Zero Config works to allow saved profiles, including WPA/WPA2/WPAn-PSK since the USB drive is R/W. No need for FBFW like with the CD-ROM versions...

Thanks to all who contributed these notes and to those involved in creating UBCD4Win... You Rule.

First of this is amazing, saves so much time using a USB key and easier to make changes.

Is there an easy way to add things like CloneZilla and ubuntu to the USB key?


Cheers

I'm still getting BSOD 0x0000007b after enabling lba and copying the files from a 2003 cd...

Any ideas?

Im getting the same

im testing with a kingston 1gig usb drive and a via c7


I get the boot menu, it starts to boot xp. You know how the windows XP logo and loading bar fade in on screen ? mine starts to fade in then freezes (you can only just see the logo cause it hasnt fadded in yet). THe lights stop flashing on the flash drive. then a few mins latter i get that BSOD 0x0000007b


Ive replaced the files from a windows 2003 r2 cd. and set my drive to LBA. Should RAMDISK.SY_ be renamed to RAMDISK.SYS ? (i didnt do this)



Any help would be awesome. as i used to boot from a USB cd drive but this no longer works in 3.11

You do NOT rename the files.
You can either replace the same name file in your source directory, or overwrite them in the output folder AFTER EXPANDING THEM. The *.SY_ is a CAB COMPRESSED file. From a command prompt you would type EXPAND RAMDISK.SY_ RAMDISK.SYS so the file will be usable to windows.

The "Fade in & Freeze" you describe sounds a lot like the ACPI problem with some older hardware, there is a setting for this in the usersettings.inf file.
To test, when you see "Press f6 for 3rd party drivers..." , press F7 and this will bypass the ACPI LAYER and may allow the system to boot, since we are dealing with usb problems to begin with, this may not effect your build but it may be worth testing.

Excellent that fixed my issue, however it now gets passed that and freezes after the windows loading bar as gone past a few times.

Slowly getting there

ok..
now i can't boot from any of my cd:s disks etc. even the vista cd..

wanted to run a dos app so i put on my bios flas boot disk and all i got was:
syslinux 3.51......could not find kernel image: linux

i'm a total linux noob.. but did this method replase dos with syslinux or something?

If you flashed your bios and something went wrong... I'd suggest you contact the manufacturer to find out how or if you can correct it.


I've deleted your other post stating the same thing... please do not cross post your questions.