Thanks for the feedback LioN - always nice to hear back when it works!!!

your english was fine!

4,752

(7 replies, posted in DriverPack Mass Storage)

Shark i think you may misunderstand what we do here.

we are not a forum that caters to noobs.

We provide DriverPacks that are added to your installation disk.
I get the impression you just want us to look up your machine, figure out wich drivers you need, and provide them to you. We have not in the past nor will we in the future provide that service. If i understand correctly what you want, you need to ask Sony for them yourself.

if you use driverpacks and find that a driver you need is not in the packs then you need to go out and find it yourself.

Once you have discoverd a driver that is not in the packs and gone out and found it yourself

then you may come back here provide the HWID for the device and a link to the driver that works for that HWID and make a request that we add to to our packs.

@abdou
please refer to the link in my signature "read before you post"
if you fail to provide the basic required info we can't help you.

this is an ICH5 chipset and will emulate an IDE controller if the proper settings are selected in BIOS.
no special steps are required driver wise to get up and running

delete the folder

the default location is windows\driverpacks or more specifically %SystemRoot%\DriverPacks

don't you have HAL issues when you use this technique?

if you create an ISO image (say from your incd disk) then the iso image will create a bootable disk even after you edit it.
so when you burn the ISO image it will create a bootable cd since the original was bootable - it really is very easy

if you use nLite or RyanVM integrator to burn your files they will automagicaly make the disk bootable.

It is incd that is a pita - I have used it - lots of extra steps like having to prepare the disk before you use it.

however the same idea applys to updateing your incd disk. you can swap out the files on it as well.
BUT then your InCD will become fragmented and slow down just like a fragmented HDD would.

as i said in my previous post

DizzyDen is correct you may simply swap out old DriverPacks for new ones in the "OEM" folder no additional steps are needed to udate the packs on your **** InCD.

however i said image when i meant incd

try this: use your favorite compression tool and see if you can extract it manually from C:\xpSource\i386\setup.ex_

it is a great idea. simple and effective. well done!
I am sure some people will like it...
however jake was wrong about me loveing it.
I like unnattended installs and this stops the install twice.
So the UWXPCD is defeated and thus useless to me.

PS i hate KTD and am not shy about saying it and telling people why as most people don't understand what it is.

but i am sure you will have others here who will disagree with me. wink

the error indicates that your source files are corrupted. specificlly setup.ex_

that is why i asked you to create a fresh copy of your XP installation disk on your HDD

InCD will allow you to do this.
Not a very clean way to do this, but it will work. (you end up with a dvd that needs defragmenting - yikes!)
you can edit an image of a disk very easily (for example you can use a program like magic ISO to update an ISO image)
then burn the iso to a DVDWR a much cleaner method.

DizzyDen is correct you may simply swap out old DriverPacks for new ones in the "OEM" folder no additional steps are needed to udate the packs on your image.

with the exception of mass storage...

there was some confusion about whether it worked with 2k3 or not
if you could test it that would be awsome!

is your disk xp or 2k3 based ???

no dizzy that thread says at the end it doesn't work. because THE FINISHER DOES NOT INSTALL DRIVERS!

this however does work ---> http://forum.driverpacks.net/viewtopic.php?id=2264

4,764

(14 replies, posted in News)

good documentation will probably lead to my codeing it...

4,765

(6 replies, posted in Other)

ok .... you posted the answer to your own question

switch to method 2

check the first post in this thread

link provided

4,767

(14 replies, posted in News)

wow that would be incredible...

we seem to have a growing audience for sysprep.

armed with that sysprep might be able to be added to base
and subsequently become a supported platform

4,768

(6 replies, posted in Other)

duplicate posts killed

4,769

(6 replies, posted in DriverPack Graphics)

Thanks for posting your results and were glad you were able to solve your problem.

your post may help others in a similar situation smile

4,770

(6 replies, posted in Other)

personally i never use nlite to integrate ryans packs although many people here do.

your problems seem to be unrelated to DriverPacks... but perhaps you will get lucky and someone here will be able to help....

my suggestion is to use rvm integrator then nLite then DriverPacks on a clean source. please report back your results.

IDK if it does or doesnt for sure because i don't have the the hardeware for testing.

the inf contains these references.


;[DriverFiles_9X]

[DriverFiles_NT_2K]
fttxr5_O.sys,,,0x20

[DriverFiles_XP]
fttxr5_O.sys,,,0x20

;;;[FilterDriverFiles]

many times 2k3 will use XP drivers but not always so i errored on the side of safety

feedback is required - anyone with this hardware care to try 2k3 and report back?

new mass is up for testing

4,773

(6 replies, posted in DriverPack Graphics)

Hi itachi,
Welcome to DriverPacks.net and thanks for posting

when you report back could you include your DPs_BASE.log (from the same directory as DPs_BASE.exe)
it contains the base version and pack versions and other important basic info (so you dont have to find it or type it out).

Hope to see you around!

not to an existing image (at least not an easy way)
however if you were to create your image with a source to which you have added DriverPacks mass storage text mode.
then your windows will natively support sata (and scsi)

Welcome to driverpacks pj

enable QSC. in base

make a new copy of your OEM XP installation disk as a source and try again.

did you make any changes to the source other than DriverPacks?