Jump to content

vyruz

Member
  • Posts

    6
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Belgium

About vyruz

vyruz's Achievements

0

Reputation

  1. Hi, I'm trying to develop a single Windows POSready 2009 (POSready = 99% windows XP) image which can be used on a lot of different hardware platforms. On one of these hardware platforms I'm running into a strange problem which causes a BSOD during boot. In this concrete example, the situation is as follows: - 2 directories containing both Intel integrated Graphics drivers: C:\drivers\GFX_Intel.20080911 C:\drivers\GFX_Intel.20091113 These 2 directories have similar files, but are not interchangeable since one directory contains graphics drivers for a certain motherboard which the other once doesn't support, and vice versa. - DevicePath key in the registry contains (amongst others): C:\drivers\GFX_Intel.20080911;C:\drivers\GFX_Intel.20091113;C:\windows\inf What's happening is that after running sysprep, windows seems to be copying the wrong file to it's C:\windows\system32 directory. Because the BSOD talks about igxpdv32.dll causing the problem, and when I go look for this file, it appears that windows is trying to use the same file from the wrong GFX_Intel.yyyymmdd directory. Any bright ideas on how to solve this? Thanks!
  2. next problem So I had the setup working inside a virtual machine. I then made a ghost of the virtual disk, and restored the ghost onto a 'real' hardware platform. After that however, XOSL wouldn't start... I've tried reinstalling XOSL but that didn't help one bit... I did try all 3 imaging 'modes' of Ghost, with one of them specifically stating that the MBR should be backed up as well, howeve the result remains the same: system tries to boot from HD0 and screen remains at a blinking cursor. I'm currently looking at the drive with ptedit but when I go to the 100MB extended partition I'm using for XOSL, the 'Boot Record' button gets disabled so I can't check the 'hidden sectors' value. Also, when booting from my Grub4DOS-equiped USB drive, I can perfectly boot all the partitions, including the extended WinPE partition. Anyone got any clever ideas?
  3. I fixed it!! Apparently the black screen with 'XOSL' on it meant that the bootloader of WinPE (BCD) couldn't start, so I started reading the 2 links that Jaclaz provided in the beginning, and indeed that 'hidden sectors' number was way too low. Funny thing is that Grub4DOS didn't care about this and worked just fine. Guess this means XOSL is not as stable as Grub4dos. After fixing that at least BCD was starting but not booting WinPE due to some minor issues in the BCD config. Just want to point out that while I do prefer Grub4DOS over XOSL in a technical way, XOSL is a lot more user friendly. The image I'm making here is intended to be used on development/testing machines to provide people the ability to easily load differen't OS's and environments (currently they're just swapping disks to achieve this). So XOSL is a lot easier for them to rename their boot options etc. So thanks to Jaclaz for providing me those links!
  4. Well this is the only forum which I could see was related to multi-booting (CD/DVD although). It was what I saw best fit for this topic. In any case, thanks for the links you provided me with, but I think they're not what I'm looking for. Since XOSL is working fine, except for the WinPE booting part. My guess is that something in the BCD configuration of the WinPE install is wrong, and the links you provided don't talk about the bootmgr bootloader. Like I said it works flawlessly when I put FreeDOS in place, it's only WinPE which is causing trouble.
  5. I hope this is the right forum to post this in, please move my post if not. I have the following drive partitioning in place: - 23GB Primary partition (NTFS) --> WinXP 1 - 23GB Primary partition (NTFS) --> WinXP 2 - 23GB Primary partition (NTFS) --> WinXP 3 - Extended partition: --- 517MB Logical partition (NTFS) --> D: drive for 1st WinXP system --- 517MB Logical partition (NTFS) --> D: drive for 2nd WinXP system --- 517MB Logical partition (NTFS) --> D: drive for 3rd WinXP system --- 1GB Logical partition (FAT32) --> WinPE 2.0 (from windows AIK) --- 9GB Logical partition (FAT32) --> shared space for all WinXP systems --- 100MB Logical partition (XOSL FS) --> XOSL2 The intention of this setup is to have 2 seperate windows XP system next to eachother, for testing different software versions. When loading one WinXP system, all partitions except that systems primary partition, the according D: drive and the shared space should be hidden. That's why I want to use XOSL2, because it can hide partitions based on what you are booting. Now loading these different WinXP systems works fine, it's loading the WinPE system that is causing me trouble. I used to have FreeDOS installed instead of WinPE, which worked just fine being loaded from XOSL from a logical partition. but due to newer systems not having driver support for FreeDOS I decided to switch to WinPE. Note that when booting this partition, none of the other partitions are visible. I tried on the same system with just 2 primary partitions (one for XOSL, and the 2nd for WinPE), and that worked perfectly, so I decided that the issue is located around the fact that I'm trying to boot WinPE from a logical partition. XOSL starts up fine, but when I try to boot the WinPE partition I just get a black screen with 'XOSL2.1.1.6' and that's it PC locked up. Any help would be very much appreciated!
  6. Hi man, I'm looking for exactly the same, can't get it working either... Could you post a bit more details about your configuration, I'll do that same and perhaps we can figure out how to get this working using our combined configs... This is what I'm doing: - Bootable USB flash drive (this will become a CD/DVD in the final product) with working WinPE environment - Local NTFS drive containing a windows XP SP2 installation So this is the output of my current F:\boot\bcd when running 'bcdedit /store f:\boot\bcd': C:\BootStores\FPMD\boot>bcdedit /store f:\boot\bcd Windows Boot Manager -------------------- identifier {bootmgr} description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} {ntldr} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {default} device ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411 -000476eba25f} path \windows\system32\boot\winload.exe description WinPE locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411 -000476eba25f} systemroot \windows detecthal Yes winpe Yes ems Yes Windows Legacy OS Loader ------------------------ identifier {ntldr} device partition=C: path ntldr description Windows XP What's happening is the following: Upon boot from USB flash drive I do get the boot menu, the WinPE boot option works fine and boots to my USB WinPE environment When selecting the Windows XP option though, it's trying to load the 'ntldr' file from my USB flash drive (tested this by putting ntldr in the root of the drive). So apparently when the bootloader is running, C: is whatever device it's currently booting from... So i tried changing the device option in my bcd file to D: by running: bcdedit /store f:\boot\bcd -set {ntldr} device partition=D: But the result was the same... If anyone could help with this that would be awesome!
×
×
  • Create New...