OverFlow wrote:

another undesirable side effect of OEMPREINSTALL=YES is you cant use hit F6 to supply a driver on a floppy

Which is not really needed anymore thanks to the DriverPacks wink

But yes, that is pretty annoying, still.
I'm not sure whether MS did that on purpose or just thought that if you are going unattended, you wouldn't supply a driver floppy anyway.

Thankfully, they finally realized floppies are so last millenium and offer the option to provide drivers on a CD/DVD/USB stick/HDD with Vista.
You cannot assume how much that pissed me off before I discovered the DriverPacks! >8(

952

(74 replies, posted in Other)

Kees030 wrote:

The only INI I could find is DPs_BASE.ini. I don't see references to folders. Could you please explain what I'm missing?

Thing is, Jaak and others including me are already used to working with the nightlies, which do feature those INIs already for quite some time that we sometimes overlook the fact that the non-testers still work with the "old" DriverPacks.

Previously, when a new DP was released, it required an update for the BASE, too.
In the future, those INIs will take care of that and also allow you to mix DP version as you please (eg. you could use an old DPMS with all-new other packs because that very combination works best for you).

As testing made a big progress recently, I think those packs aren't too far from a public release now smile

953

(4 replies, posted in 3rd Party DriverPacks)

Instead, I'll just move you to our third-party DriverPacks forum, which is the right place for such stuff smile

jtdoom wrote:

Hi

in NLite, there are two settings wich will kill the process.

UNattended setting > OEM Preinstall >> defaults to enabled, and should be DISABLED
Therefore, check WINNT.SIF
the line has to say this, OemPreinstall=No.
If it says "YES", method 2 textmode is not going to work.

another option in Nlite, will cause DPs_Base to throw error, SETUP.EX_ not found
This is caused by this one
Operating system options > Manual Install and Upgrade
If you remove this, building a method 2 cannot work.

Are yopu sure about both of this?
For #1, I would assume the BASE re-sets the parametre properly (hence, you should always nLite before BASEing).

For #2, I was ripping that part out for a very long time to save valuable space on my CD (have moved to DVD now, if you remember), and seeing as I always used M2, I'm unsure about whether it would really break it.

Things may have changed in the past so I may not be up to date here wink
Anyway, it certainly does not hurt follwing your advice, I'm just uncertain whether it is absolutely vital...

ferny wrote:

@ Helmi:
I have used both VirtualPC 2007 and latest version of VirtualBox.  Same problem with both of them.  This is the first time I have encountered this problem and I have done various slipstream/nLited/DriverPack installs before.  It could have something to do with my new motherboard (Asus P5B-Dlx).  Maybe something with AHCI?

No, the VM is completely (apart from your CPU) independend of you real HW, meaning it will use its own, generic HW, hence it cannot be a compatibility issue with your actual HW.

What you could do, though, is trying to get the disk run in yoru real system.
As you will only be prompted to install after a successfully loaded TM setup, you will not endager your current installation, but you can make sure it will load all TM drivers properly.

ferny wrote:

When I test my install using DP_MassStorage_textmode = "yes"  on a virtual machine it gets stuck right at the end of  textmode portion of setup (Setup is starting Windows...).
With  DP_MassStorage_textmode = "no" the install works fine on a virtual machine.

That is very unusual, I'd say.
Generally, none of the MS drivers are needed on a VM (which one are you using, btw?), as the drives are emulated on default IDE controllers, for which Win already provides drivers/support out of the box.

You may want to double-check your ISO image for any problems, or maybe even your system's RAM.
I cannot remember any hangs during the textmode phase while testing on my VM, and I do run a lot of tests smile

jtdoom wrote:

OH yes, you need textmode for "live" machines.

Well, only when you do not use an ordinary IDE controller for the boot/install HDD. wink

Since you said it's SATA, yes, you will need the TM drivers.

spidercop wrote:

why dont u make e compleet driver pack with all the driver pack in it then u can have beter compresion of the file

Hardly.
We are already using a Solid Archive to save the most space.
As all DriverPacks are already groupd into quite large packs that do contain a lot of hardware, combining them all into one large file would probabaly save some additional 2% at best.
Those 2% wouldn't gain you much, if anything, however.

beter download speed

On the contrary!
Firstly, file size hardly has any effect on the actual DL speed (not counting very small files at 1KB, obviously), however, it means you will have to DL the whole large pack even when only one single driver file is added/updated.
Not very efficient!

en more userfriendly u can then download driver base en the compleet driver pack in on go

It shouldn't really be that much efford to DL the handful of files there is.
Compared to how much efford and time the DriverPacks already save you, that is negligible.
Granted, an automated updating/DLing of newer files would be a nice addition to the Update Checker (currently, this only works for BASE), but seeing as the DriverPacks get updated once a month at best, I think one can easily deal with the current situation.

antonio_king wrote:

I've redownloaded over and over again but still getting CRC failures.
So looks to me like corrupt drivers!

Or a corrupted HDD or corrupted RAM on your end.

Not trying to blame you, but I haven't had a corrupted DL from here in a long time, and, judging by their silence, this is also true for other members smile

I agree, though, that some MD5 sums would be great to have (as we do for the 3rd party DriverPacks).
Did you try 7-Zip's "Test Archive" functionality yet?

AJP wrote:
Helmi wrote:
AJP wrote:

The link for drives of TV is broken.
Somebody can arrange?

Fixed now, try again, please!
smile

Thanks a lot, it is functioning. wink
This forum is very good. I loved
smile

You're welcome! big_smile

You can always go directly here to DL the files, too:
http://3rdpartydriverpacks.thesneaky.co … 2/?C=M;O=A

Just in case some others don't work and the entries on the first post haven't been updated, yet.

AJP wrote:

The link for drives of TV is broken.
Somebody can arrange?

Fixed now, try again, please!
smile

961

(7 replies, posted in 3rd Party DriverPacks)

jtdoom wrote:

Those that tested this, can you tell us what happened?

I can only second this notion.

Feedback is essential, folks!

If you don't tell us how it worked out for you, we can never optimize the packs and hunt down on bugs.
This is a very community-dependant project and in the end it is you who profit from it! smile

bombayh3at wrote:

The only new idea I found from searching around was trying a bios update, which isn't exactly the ideal solution on a Vaio laptop.

Why not?
Just curious, because I have done several updates on my laptop so far and it wasn't any different than for a desktop system.
Then again, IDK how Sony handles this and whether they actually offer updates...

mr_smartepants wrote:

@Bâshrat the Sneaky, would you like me to create one?  Lots of pictures?

I'm sure he wouldn't mind at all smile

If you have the time, please, have a go at it.

jtdoom wrote:

hehe
when one write Bee Tee Ess here it become Bâshrat the Sneaky

and dee pee ess becomes DriverPacks

Pure magic, I'm tellin' ya! smile

BlackNinjaVirus wrote:

I could get this all done easier with Knoppix DVD and a 1MB download and compile.
But most do not have a DVD in the office, and I couldn't download if there is no internet.

FYI, Knoppix also has a CD version out.

965

(12 replies, posted in DriverPack Sound)

Oh, we have some sort of beta how-to-do-it uo there somewhere.
Just have a look for the stickies, I know I have seen one wink

966

(12 replies, posted in DriverPack Sound)

damo wrote:

Maybe a few lines for the newbies would be nice to understand how DP works! i think on a help button for example or place a few instructions at the download sections, because i cant found it NOWHERE in the forums or on the entire site!

I guess  total newbie wouldn't even get the idea to unpack anything (nor would he be capable of, as it requires 7zip).

In any case, yes, a proper documentation is (still) in the works, however, we prioritized working on the actual programme rather than some notes.
Not much use in these if there are still bugs in the software, eh?

CLOSED by request.

Shoot me a mail if you want this reopened (because you tested it or something...)

Unless I'm totally mistaken, this has already been added to the latest Nightly by muiz.

Of course, you are not to blame because you didn't know smile
Just informing you we've already got this covered.

drewmie wrote:

Also, I noticed that the following version of Windows was detected:

Windows XP Professional -  Retail SP2 detected.

But I'm using a corporate version.  Is that a problem?  Is there any reason to treat the corporate and retail versions differently?

No, the Corp version is just a Pro without the need to activate.
Apart from that, it is identical (and it is not specifically referred to as Corp, hence it gets detected as Pro).

Lastly, if I'm integrating RyanVM's Post-SP2 updates using Ryan's official integrator, I assume I should do that first, then integrate Driver Packs second.  Is that correct?  Thanks for any help!  Driver Packs rock!

Yes, the DriverPacks should always be the last step before creating the ISO.

You will need to install the HDA hotfix from MS to make any HDA device work.
AFTER you have installed that, the real SC driver can be installed.

Ususally, this is handled by the DriverPacks.
If you use an UpdatePack which already contains the HDA hotfix, this step will be skipped because unnecessary.

Please post your logs to see whether the HDA detection worked properly.

hilander999 wrote:

What has to be done to add this driver???

Posting a proper request.
I edited your topic accordingly.

Now, you'll only have to wait...

BigBrit wrote:

Jtdoom: I have had a couple of problems with KTD, sometimes it takes 5 mins and sometimes it takes 5 secs.
I admire you guys for the programming, I am a hardware tech and have enough problem with that.
If you need someone to test some stuff I can help with that ???

Sure!
If you like to, you can become a member of the Testing Team, meaning you will get to test the nightlies - both BASE as well as DriverPacks before they get released.

The more testers we have, the larger hardware base we can test things on.
Since a VM cannot emulate the hardware, we can only properly test those drivers we actually have the HW for.
With a limited amount of testers, only the most common HW will usually get tested.

Try to PM/email Bâshrat the Sneaky about it so he can unlock your account for access to the Testers sub-forum.

kelaniz wrote:

No problem. Glad to be helpful, even if I did reply to a post from 9 months ago smile

Hey, it's a sticky, so it never gets "old" wink

Did you already try applying a BIOS update?
Chances are (check the changelog) even the SATA controller got updated.

Maybe this is indeed a more serious problem/bug...

Thanks for your advice, kelaniz!
I edited the first post accordingly and added even a further bit of info smile