Jump to content

Bâshrat the Sneaky

Member
  • Posts

    5,580
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Belgium

Posts posted by Bâshrat the Sneaky

  1. Without DriverPack MassStorage, loading all txtmode mass storage drivers from the CD (cannot be disabled, hardcoded setup routine) takes already more than one minute. If you include DriverPack MassStorage, that will easily increase to 3 minutes and longer... Though this is rather 'presetup' than 'setup', people who have automated the partition selection/formatting part(s) of setup, might have some notifiable reduction in installation time, certainly when these installations are being used in corporate environments.

    EDIT:

    P.S.: it's txtsetup.SIF, not txtsetup.INF! ;)

  2. Anyone know the difference between cabarc.exe (61k) and makecab.exe (77k) ?

    Their internal help suggests cabarc is more robust, yet smaller?

    Both have the same version# 5.1.2600.1106 from ieak6.exe (6.0.2800.1106)

    Am pretty sure Win2K doesn't have makecab.

    PM RyanVM about that. I once knew it, but I'm 300% sure he DOES know. ;)

  3. Small question:

    I managed to integrate these drivers perfectly (6.67) with nLite 1.0RC1, but as I'm a big fan of the BTS driverpacks, I wanted to add these packs to my cd. I did think integrating the masstorage drivers and the chipset drivers might mess up the installation, so I chose _not_ to integrate these packs.

    However, when using the install cd I got an error message very quickly stating nvataraid.sys was missing. So I guess I shouldn't have integrated these packs.

    Is there a way to integrate the 6.67 with nLite AND using the BTS driver packs (or some of them) without breaking the install? (f.e. by manually re-adding some lines in TXTSETUP after BTS integration has finished maybe?)

    I hope BTS is able to tackle the problem with his (masstorage or chipset-)pack himself, because they are really priceless - my cd's however turn up worthless when I use them on an nForce4-platform :(

    THX in advance!

    Zl.

    Hm... please post your problem in detail in the DriverPack MassStorage forum! ;)

  4. Does your laptop have a floppy station? If yes, this is probably the easiest solution.

    If not, you'll have to slipstream the drivers. A tutorial can be found in this forum's "Read this first" sticky, the easiest is using my DriverPack MassStorage: check my signature.

  5. My theory seems to be incorrect, since I cannot edit this topic's title either and this one has been started June 21 of this year, months before that (temporary?!) policy of you, xper.

    So it must be ... a damaged database? I don't know... I hope you can figure it out.

    EDIT:

    an example of another error:

    mySQL query error: UPDATE ibf_topics SET title='REQ | Xircom CardBus driver?',description='SOLVED' WHERE tid=51555

    SQL error: Incorrect key file for table: 'ibf_topics'. Try to repair it
    SQL error code:
    Date: Sunday 09th of October 2005 01:07:04 PM

    As you can see, the exact same error... it must be the "incorrect key file for the 'ibf_topics' table" that is causing this.

    Could you fix that?

  6. Never mind, it's now in EVERY topic I try, at least in the DriverPack LAN forum.

    EDIT 1: In the DriverPacks General Discussion forum there aren't any problems.

    EDIT 2: Nor in the DriverPack MassStorage forum.

    EDIT 3: No more errors.... :blink::blink::wacko:

    EDIT 4: Hmm... it seems it just doesn't work for *SOME* topics...

    And you see it coming here, xper... it's those topics that were created during the time that you disabled topic descriptions... It *must* be that. Or am I out of line here? :P

  7. mySQL query error: UPDATE ibf_topics SET title='PROB | RIS: nVidia NIC driver not detected during RIS-boot',description='' WHERE tid=54344

    SQL error: Incorrect key file for table: 'ibf_topics'. Try to repair it
    SQL error code:
    Date: Sunday 09th of October 2005 12:01:09 PM

    This is the error I got after trying to edit the topic title of this topic. I tried it 5 times, each time with the same result.

    I tried to edit the topic title of another topic in that same forum: no problems.

    I hope you can fix this without too much problems, xper?

  8. I'm pretty sure the setting is in the registry. :)

    Indeed.

    Use RegSnap/RegShot...

    1. Enablee your 2nd monitor.

    2. Run RegSnap/RegShot for the first time.

    3. Disable your 2nd monitor.

    4. Run RegSnap/RegShot for the second time.

    5. Let RegSnap/RegShot compare the two registries and voila, there is the key you need.

×
×
  • Create New...