Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

  • Country

    United Kingdom

Everything posted by ZaForD

  1. Hi Bezalel, All you need is SP2. I use my MCE Remote Keyboard on XP Pro all the time. You just plugin the eHome Transceiver, let XP Pro find it, then switch on the Remote Keyboard.
  2. @ Bezalel & FreeStyler, I've just collected the OEMBIOS file set from a new [Pro SP2] Packard bell, these files are different from the old set I sent you [Home SP0]. Do either of you want them for your collections ?
  3. OK Guys, I tested the Hedy OEMBIOS set in both Home and Pro on my test box, and both activated, I tried it on Virtual PC and again the Pro failed. So I'm guessing its a Virtual PC thing. @ FreeStyler, Thanks for the NEC files, and for passing on the Virtual PC info.
  4. @ Bezalel, FreeStyler, Severach, I'll explain what I was doing, which should answer most of your questions. I was making two OEM Multi-Boot disks, one for Home and one for Pro. Each image included OEMBIOS set, the PID for that set or the Microsoft System Builder PID, oemlogo, info, wallpapers and themes [if available] As I added each image to the disk, I tested it in VirtualPC. Which was setup to dual boot, and had the BIOS modifed with the SLP for that OEM. I know its never a great idea to test two different things at the same time, so any problems I found i.e. PID failing, wallpaper/theme not displaying I noted down so I could look i to it later and continued on with the next install. All was fine till I tried the Hedy set. Both Home and Pro images installed fine, except the Home preactivated but Pro didn't. Which was strange as the hardware/BIOS were indentical [Dual Boot VirtualPC] I rebuilt the Pro image making sure I used the correct OEMBIOS set and installed it again, with the same results. Now my Multi-Boot disks are complete [i think] I'm going to test them on a real system. I'll start with the Hedy installs and report back.
  5. Hi Guys, I'm not sure if this a warning or question. I've read a few times in this thread that you can use a Pro OEMBIOS set on a Home install, and vice-versa. I myself have used a my Dell Pro set to install Home on an old Dimension testbox. Recently, I've been playing with a multi-boot disk, everything seemed fine till I tried the 'Hedy' set. They worked with the Home install, but failed on the Pro. Has anyone else come across this problem. I'm wondering, if its a case of the Pro sets will work on all installs, but the Home sets only work on Home.
  6. ZaForD

    need a sig

    @ WolfX2, I love that Chunkyboy sig. Keep up the great work.
  7. @ bober, How many installs have managed to get on your CD with the DriverPack ? I haven't manged to get it to fix a CD yet.
  8. @ bober, They're in the Multi_Boot_tools folder of the DriverPack base folder. I didn't test the mass storage drivers as I was testing it on an old PIII with standard IDE ports.
  9. @ bober, Thats strange, It worked here on a Dell and an eMachine ???? Then I rebuilt my disk and wrecked it. This is the info I followed, i think its the link you were looking too. Multi-Boot + Driver pack. I'll be building a new Multi-OEM disk on the weekend, so i'll be able test building it with the Driver Pack again.
  10. Hi cyril_for_ever, Try removing the bootfix.bin from your i386 folder. I think it has something to do with that message.
  11. @ bober, I had it working on my Multi OEM Boot disk, till I got the NTLDR problem. This is what I did: Copied OEM Pro source files to HDD. Updated with RVM's Addon Pack, using the Integrator. Added BTS's Driver Pack, using his new Base 6.0. Then I used the resulting files as the source for creating my Multi-Boot disk, as per the guide. I added a $OEM$ folder in each install folder, for OEM specific files. And moved the OEM folder in the root of the disk. This worked a 5 or 6 times before I had any problems, so I don't think it had anything to do with RVM's pack or BTS's driver pack. I couldn't get it to fit on 1 CD though.
  12. Hi Randy, I'd leave out this step, to see if everyting eles works.
  13. Hi WolfX2, Some nice userbars there, I hope you don't mind me stealing a couple. p.s. I see your GFX skillz are better than your counting.
  14. Hi carheim, I believe Microsoft has blocked all COA keys now, so you'll have to phone them within 30 days to activate your copy of Home.
  15. Hi Guys, I think this problem might have something to do with the 'txtsetup.sif' One my last build 'NTLDR' was in all my UA disk folders, but it couldn't be found on install. In the test I just did, the base SP2 build, kept reporting files missing on install. Files that when i checked were in the i386 folders. The second RVM build, is still installing and is at T13 now in Virtual PC, without any errors. I compared the files in each boot folder and the two 'txtsetup.sif' files and there are very different. Apart from the extra files added by the update pack, the layout is very different. Anyway, back to trying to work out where to put my $OEM$ folders. Thanks for the help.
  16. @ bober, I notice your menu uses bin files not dat files. Is that just the way they're named ? Or do they work differently ? I'm begining to think something has changed in the setup between SP1 which the guide covers, and SP2 that i'm using. I'm about to do a little test, by attempting to make two Multi-Boot disks. 1. With an Orignal OEM WinXP Pro SP2 disk. 2. With the same disks files, but updated with RVM's pack first. I've got a sneaking feeling the second one will work, but the first won't.
  17. @ TD, sssssshhh.... Thats a risky topic,
  18. @ bober, By boot menu, do you mean the cdshell.ini ? I've deleted and formated over my orginal. So i'm using the one from the download section here. Unedited incase it was my version that was messing up. @ LiquidSage, The PC boots, shows the splash screen, displays 'Press Enter to boot from DVD'I press Enter, then at main menu press 1 for XP Pro menu, then which ever option I choose I get the NTDLR error. I'm using CD Shell 2.1.6 On this attempt the only tidying i've done is to remove the 'unattended.txt' 'bootfix.bin' 'txtsetup.si_' 'setupldr.bi_' and '.bak' files, as per the guide. My original build had RyanVM's pack included, this one has nothing. Can't check this as the Multi-Boot CD with the $OEM$ folders have been deleted. Again, no winnt.sif in this attempt. I'm not sure what this means, I made a .bat file which has the ISO info copied from the guide. I've double checked my old ones and created new ones. I'll see if I can get hold of them.Thanks for the quick replys guys. Its the only good thing thats happened on this Multi-boot all weekend.
  19. Hi flupke, I've been using MCE since the 2002 version, and as ScubaSteve said, it like XP will run [slowly, but still run] on pretty low spec boxes. The only parts of MCE that you'll have problems with are DVD Playback and Live TV. Both of which are very heavy on CPU load and use hardware decoding and encoding in real MCE boxes. FYI, I have MCE on old Thinkpad 570 PII366, 128mb RAM, 6Gb HDD. It dosen't play any TV or Video but works perfectly as a remote media hub / RDC terminal for the other PC's here. Plus, booting straight to the MCE GUI makes it look very flash too. B)
  20. Hi Guys, This is really starting to drive me nutz now. I have three UA disks, all OEM Pro and all work prefectly. I thought i'd get abit flash and have a go at making a Multi-Boot CD of them. So I followed the Multi-Boot DVD guide and ended up with three working UA disk on one CD. I then started working out where to place my $OEM$ folders, when I first got this error on booting. CDBOOT: Couldn't find NTLDR It seemed strange as the files i'd just changed were in the $OEM$ folders, but didn't worry about it and created another ISO. Which also failed, as did the next 5 or 6. Anyway to cut a long story short: Over the last two days, i've since scraped the whole thing twice, then I started again on a newly formated PC, and started again on a differnet PC. Using the same Orignal OEM CD for formating, installing and the Multi-Boot CD, again following the guide to the letter. After these failed with the same error, I tried using my Retail CD and downloading all new files from the links in the guide, but I still keep getting this same error. I've seached through this forum, but most of the threads are about Win2K3 having these problems not XP Pro SP2. Has anyone got any answers ? As I said earlier its driving me nutz....
  21. DarkAsHell, The easiest solution is to use the version provided by your laptop manufacturer. Make your UA disk using that version and use your OEM key in the winnt.sif. It can be done using your Upgrade disk, but its alot more work and you have to edit some system files. Theres also some disupte as to whether we can tell you which or how to edit those files.
  22. Hi affiray, I've had no problems making an MCE2005 unattended disk, you just add the contents of the second disk to your root folder, make your winnt.sif and burn it to disk. The place where i have had problems is updating the disk, both nlite and RVM's pack brake my MCE install. So i use the /inetgrate switch as discribed in the Guide, and then RunOnceEx for Rollup1 and the April Update. Hope it helps. B)
  23. Hi Guys, Another Computer Report for you: The PC is badged as an Advent, they are made by NEC and sold in PCWorld/Dixons here in the UK.
  24. First off, theres no panic about these drivers, guys. The system in question is quite happy running under 32bit XP Pro, I was just testing an eval copy of x64. The MoBo is a Gigabyte K8NS Ultra 393 w/ Sil 3512 Controller. I found 64bit drivers for all the hardware except SATA, I had to use the 3514 [i think] drivers which worked 99% of the time. The printer is a HP PSC 1215, HP only released a 64bit driver for this in march of this year. HP [as fair as i'm aware] still don't have Win2K Server or Win2K3 drivers for this printer. Fortunately one of the guys here was able to modify HP's Win2K drivers.
  25. I don't know either. I'm gonna try a clean manual install, to try see which drivers are doing what. If that works out fine i'll try making another UA disk from scratch.

  • Create New...