Jump to content

shinomen

Member
  • Posts

    14
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About shinomen

shinomen's Achievements

0

Reputation

  1. How's it going with adding back in the txtsetup.oem files for support with bartpe?
  2. @ryanvm: I guess it means that you slipstreamed wmp10 into your I386 setup files and used winnt.exe to install windows and winnt32.exe. @Gnome: I did an install using winnt.exe and everything went fine. Wish I could get it to work with winnt32.exe, but I guess that would most like be a problem to bring up to Microsoft.
  3. Thanks, I've been posting in your forums with what I've been finding http://www.ryanvm.net/forum/viewtopic.php?t=131 but haven't come up with anything. I wasn't trying to down your pack, I think they are great, I just wanted to point out that it was only happening with the medium and full pack for me. Thanks
  4. I've been having alot of problems slipping in ryanvm's medium and full pack, so I decided to go with his lite pack since it slips in and gives no errors during setup. The errors I would get with the medium and full pack was: So the idea was to go with the lite pack and then use the windows media player 10 slipstreamer. Well after slipstreaming the windows media player 10 into my installs, I'm now getting the same error I was getting with the medium and full version of ryanvm's update packs. Any ideas on why this might be happening? I have my installs setup to use winnt32.exe that I execute from a bartpe disc. Any help would be great. Thanks
  5. Has anyone come up with a fix for this? I'm also using winnt32.exe to launch setup from bartpe, and I'm getting the same Cannot Load Interent Configuration Library ICFGNT.DLL error. Thanks
  6. That would be great. Thanks. You should try bart pe one day, it's real simple to setup and when you see it add the drivers you will be amazed at how simple it really is. thanks again
  7. Yeah, it was for you. I just wanted you to put them in there so that I could throw the entire pack into the bart pe SCSI folder. Thanks
  8. I think you should include all the txtsetup.oem files (if there are any) that come with these drivers.
  9. Yeah, your talking about the UBCD for windows driver pack right? Yours is more complete (and seems to be updated more often) so I was trying to stick to using the same driver pack that I integrate into my windows installation as I integrate into bartpe. I saw that you have a tutorial comming soon on this subject, just wanted to see if there was any more information regarding this. Thanks.
  10. Is there any tutorial or reference that I could got buy for adding the mass storage driver pack to the BartPE CD? BartPE now has an option to drop your mass storage drivers under a single folder and it will parse through and add them to the CD. The problem is that it does this using the txtsetup.oem file to add them to the CD, which is missing from most if not all of the drivers folders in the mass storage driver pack. Any help would be appreciated. Thanks.
  11. Just found these driver packs today am excited to get them but I keep getting the following message when trying to download Warning: Cannot modify header information - headers already sent by (output started at /home/bashrat/public_html/includes/inc_dp_vars.php:279) in /home/bashrat/public_html/includes/inc_file.php on line 26 Any idea when this will be fixed, or is there an alternative (mirror) to download these from? Thanks
  12. So will this also work for integrating these mass storage drivers into an existing windows xp install CD? That way windows setup will have all these drivers available during installation without having to put in the txtsetup.oem floppy during setup. Thanks
×
×
  • Create New...