Learn how to create a bootable Windows PE 3.0 USB drive. First you you create the bootable USB stick, then you copy the WinPE 3.0 files to the drive.

Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site. Or read our to learn how to use this site. Exactly in the subject. My dad has entrusted my with the task of trying to fix his old IBM computer.

Install Root Enumerated Driver Live Suite. Actually, he really doesn't care anymore, he just said if I can fix it, that would be good. So I loaded my installation copy into a USB using WinUSB Maker (Beta 2, if you need to know.), and it worked. My USB loaded into the laptop fine, and it actually installed. After the setup finished, which took more than 30 minutes, I restarted the computer as it probably said, after after boot from the USB, it stated NTLDR is missing, press any key to restart. Tried again WITHOUT the USB, and it still had the same results, instead of it being 'Any Key', it was Ctrl+Alt+Del to restart. I dunno what's going on.

The boot order is as follows, 1. USB HDD (My USB). Legacy Floppy Drives 4. ATAPI CDO (Buncha numbers that probably is the serial.) 5.

IDE HDD1 EXCLUDED FROM BOOT ORDER IDE HDD2 ATAPI CD1 The weirdest thing is that NTLDR is ON the setup USB I made. I don't know why it can't find it. Below are the main items and folders that are on the drive: $WIN_NT$.~BT $WIN_NT$.~LS cmpnents DOCS I386 SUPPORT VALUEADD $LDR$ AUTORUN IO.SYS LAST SESSION LAST SESSION_U MSDOS.SYS NTDETECT NTLDR (Wow, really?) README SETUP SETUPXP SMARTDRV TXTSETUP.SIF WIN51 WIN51IP WIN51IP.SP2 WIN51IP.SP3. No, I did not run a diagnostic, and the computer originally ran Windows XP.

Professional if I recall correctly. I had no idea what the problem was with it, with the only clue of NTLDR is missing on boot. My dad had stated that there is no OS and it is a new hard drive. I don't know if that's exactly true, but I have already tried various NTLDR fixes online, none of which that work. Not working meaning, well, other system files were missing which was stated by the computer.

I was able to run DOS with a USB drive I affixed with DOS, so at least I know that works. The computer, for all I know for now, is an IBM Thinkpad from around 2004, I think. My friend gave me his own XP installation disc, in which I copied the ISO on to my computer and gave back to him.

It's literally a retail box with the installation disc of Windows XP Professional included with Service Pack 3. Don't worry about the serial code, I have that covered.

Hey everyone. I'm working with the AT32UC3C-EK board, trying to get a virtual COM port going on the USB_VCP (J27) connector. My PC is running Windows XP SP3.

When I connect the board to the PC's USB it comes up as an unknown device in device manager. I've tried updating the driver by pointing it at the at32uc3xxx_cdc.inf file and I tried downloading a 3rd party driver. The PC never figures out what the device is, though. Let me know if you have any ideas for getting my PC to recognize the board as a COM port. I don't have control over the VID and PID for this.

There is an AT32UC3B between the USB port and the AT32UC3C that I am programming. That UC3B is pre-programmed with UART to USB firmware. Is there some way to see what VID and PID it uses without having the firmware? UPDATE: In device manager open the properties for the device, then the details tab. The VID and PID show up there.

My board is using VID: 03EB and PID: 2310. I edited the.inf file with the new PID and it works. Thanks very much for the help!