need txtsetup.oem

onlyonemanonlyoneman
edited August 2007 in Science & Tech
trying to install xp on to a SATA drive. went through all of the stuff about getting the drivers and such on a floppy blah blah blah. i press F6 to load the drivers and all i get is "the file txtsetup.oem could not be found."
i managed to find an article on what this file does, while i didnt understand much i was able to understand that i need txtsetup.oem file specific to my chipset. herein lies the problem. i dont know where to find it

the MOBO is a biostar K8. model number K8M800-M7A

can someone please help!

Comments

  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited August 2007
    ftp://ftp.biostar-usa.com/drivers/IO/VIAVT6420FLOPPY_300A_WINNT42KXP.EXE
  • onlyonemanonlyoneman
    edited August 2007
    ok, got that squared away. thank you Primesuspect.

    now when the disk is read i get the message:

    "The file txtsetup.oem caused an unexpected error (1024) at line 1747 in d:\xpsprtm\base\boot\setup\oemdisk.c" :mad::mad:
  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited August 2007
    You may have a bad XP install disk, or hardware issues. Have you successfully installed XP on this machine before? Is this a legit XP install disk? That path "xpsprtm" sounds like a rtm copy (release to manufacturing).
  • QCHQCH Ancient Guru Chicago Area - USA Icrontian
    edited August 2007
    Could also be a slightly off CD-ROM drive.
  • onlyonemanonlyoneman
    edited August 2007
    primesuspect wrote:
    You may have a bad XP install disk, or hardware issues. Have you successfully installed XP on this machine before? Is this a legit XP install disk? That path "xpsprtm" sounds like a rtm copy (release to manufacturing).
    i just bought the xp disk froma local store but it does have a red band across one ond of the booklet that says "for distribution only with a new PC" i thught that was a little odd but i didnt thnk it would make any difference. should i take it back?
  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited August 2007
    Yes. They sold it to you illegally - it is an OEM verison they're supposed to only sell with new hardware.

    Besides the point though - it should install despite its suspicious legal status. Q may be on to something with the defective optical drive. Do you have another drive you can test?
  • onlyonemanonlyoneman
    edited August 2007
    primesuspect wrote:
    Yes. They sold it to you illegally - it is an OEM verison they're supposed to only sell with new hardware.

    Besides the point though - it should install despite its suspicious legal status. Q may be on to something with the defective optical drive. Do you have another drive you can test?


    yes i do. ill try that now. thanks for your help so far. ill let you know how it turns out.
  • onlyonemanonlyoneman
    edited August 2007
    will it cause any problems if i go ahead and use this OEM version of the disk?
  • RyderRyder Kalamazoo, Mi Icrontian
    edited August 2007
    onlyoneman,

    This install disk...does it have the Microsoft logo and a Certificate of Authenticity?

    You should not need any floppy drive unless you are running raid, or you are using a SATA port off another controller besides the chipset.

    Do you have the SATA ports set to Native IDE mode?
  • onlyonemanonlyoneman
    edited August 2007
    yes it has the logo and cirtificate. no doubt its a authentic windows disk.

    someone else told me the same thing about not needing a disk, but this MOBO is a couple years old. you dont have to use a floppy anymore, but in '04 or '05 when this MOBO was made you did.
  • onlyonemanonlyoneman
    edited August 2007
    primesuspect wrote:
    Besides the point though - it should install despite its suspicious legal status. Q may be on to something with the defective optical drive. Do you have another drive you can test?

    tried another drive. still the same thing.

    however: i had previously replaced the txtsetup.oem file on the floppy i made (using a utility in the drivers .zip file i downloaded from the manufacturer's site) with a txtsetup.oem file from the driver disk that originally came with the MOBO. the first time i tried to install after switching CD drives it actually loaded the driver, but then i got another error message...which i didnt write down. the strange thing is that i havent been able to recreate this. now i just get the same old thing i was getting with the other CD drive...i dont know. im lost
  • RyderRyder Kalamazoo, Mi Icrontian
    edited August 2007
    Do you have the latest bios for the board?

    This is a 754 board, so those SATA ports are on a separate controller from the chipset.
    I think you have a bad Floppy drive/cable/disk.

    If you have another system to work on...you could slipstream the drivers.
  • ThraxThrax 🐌 Austin, TX Icrontian
    edited August 2007
    It's probably a bad floppy. Those OEM disks are absolutely terrible.
  • stoopidstoopid Albany, NY New
    edited August 2007
    I was working on a PC recently that wouldn't boot windows, so I tried a repair install (which is basically an installation over the existing installation). Got a lot of read errors during the file copy at the start of the install. After trying several times, running DFT hard drive test, and failing several windows installation attempts I finally ran memtest and the memory was shot. Replaced with a known working stick and no problems.

    So, test the memory. What was strange is the memory just suddenly died. Usually a power surge would take out more than just the RAM which is why it took me so long to finally decide to test it, considering everything else seemed fine.
Sign In or Register to comment.