too.........

can you have the better source ?
i'm need it to use for install my dv2107tx
i'm can't download from other like free store hosting like rapid,mega or any because my country are use slot full always


or anyone have ideas to fix this error ?
thanks..........

Well let me know if somebody still need this Directorys


C:\SWSetup\HPQPDP (715 MB)
C:\SWSetup\QPW (76.8 MB)

As i can see on my dv2120us. Both refer to Quickplay 2.3 version. Just let me know and i will be happy to rar that stuff and upload it somewhere.

Cheers

Hello Friend,
Can you please upload the those files for me please!!
I dont have any copy of those files..As my C drive was wiped out due to a mistake

Sure I will upload those tonight .. Are 8 files of 96mb each and the last one of 9 mb. I will upload them to megaupload.

Thanks a lot!
I would be really glad to complete this

hello Digg
thanks for the quick reply.
i really appreciate ur help!
Thanks a lot again!
I eagerly await for your post!

Well here are the files.

http://www.megaupload.com/es/?d=0YF610CB
http://www.megaupload.com/es/?d=KDG1U81H
http://www.megaupload.com/es/?d=9L5LBAH9
http://www.megaupload.com/es/?d=OAFK6CJ3
http://www.megaupload.com/es/?d=HWSLUZIU
http://www.megaupload.com/es/?d=U1DX1XQH
http://www.megaupload.com/es/?d=Z71POIP9
http://www.megaupload.com/es/?d=4V9I7K6F
http://www.megaupload.com/es/?d=3TYPR0P3

Let me know if you have any problem with any file..

Thanks a lot!!
Just started downloading..!
I really appriciate your help.
Tx

Same things as the other uploaded QP23 rar, HPQPDP/data2.cab has a CRC error. I'm beginning to wonder if that particular file has some bit pattern in it that megaupload filters for and damages. Could someone upload just HPQPDP/data2.cab, or perhaps send it to modemboy so he could host it? Much thanks!

Has anyone seen the error "$Macro Vision Fail!" when they try to play a DVD in QuickPlay Direct? If so, how did you fix it?

Hi Guys!

Brilliant Forum here before I say anything else, has been really helpful getting me started and now onto the problem

I have just tried updating QuickPlay and QuickPlay Direct from version 2.0 to 2.3 on my HP dv8295ea laptop
I was able to install Quick Play (for Windows) and that works fine however when I try to install Quick Play Direct it always gets to a certain point (when it seems to be installing NAMSetup.exe) when it stops and comes up with the following error:
- ComponentMoveData had the following error:
- Component: QuickPlay COmponent
File Group:
File:
Error Number: -2147418113

My Laptop has Dual Hard Disks but disabling the second one doesn't fix the issue nor does removing the QuickPlay partition.
I'm out of ideas... any suggestions?

Riddick

P.S. Anyone know why WinRar tells me that Data2.cab is corrupt yet 7Zip merely lists it as broken... from both Download Sources

I think a lot of us are getting the same error. Someone requested a link to just the data2.cab file.

I'm a moron and, in trying to reclaim as much HDD space as possible (I'm anal like that), I deleted both the recovery partition and the "inexplicable" and "unpartitioned" 1GB volume without realizing it was the QP partition. I am considering biting the bullet and buying the CD from HP since all other paths are thus far leading to a dead end, and I don't have the HPQPDP folder on my drive.

Also, can anyone tell me why is there no data3.cab? Is this normal?

First of all, thank you everyone for your time and effort in making right what HP should have done in the first place. I just purchased a refurbished dv4000 (p/n in sig) which came loaded with QP2.0, which coincidently did not work out of the box. (I also made a set of repair disks which my computer says are not the correct ones for this model…lol)

I’ve tried to install QP2.1 three times; first I got the blue screens mentioned earlier, and the second and third install I got the black screen and then freeze condition. Neither time could I start QP with QP buttons. Actually after I installed QP2.1 Direct (the second time), I had the boot select screen come up with a Windows XP embedded option.

Also of interest, my laptop came loaded with BIOS F.15, which I can't find anything about.

I want to try QP2.3, but I am having the same problem with the Data2.cab reading as corrupt. If you look at the file in WinRAR program, it reads the size as 298,115,072 but the packed size is 600,092,706. Has anyone uploaded the Data2.cab file?

I found this thread very useful for getting info about how Quickplay 2 works. I spent some hours figuring how to get my HP DV8357ea to work properly with Quickplay, Linux and WinXP. Now that I have the system working properly, I wanted to share my experience with you:

In my case, I have Windows XP installed on the primary HD and Linux on the secondary (actually, just on part of it, an extended partition). XP came preinstalled, after that i installed Mandriva Linux, which by default installed its boot-loader LILO in the Master Boot Record (MBR). Of course, this made QuickPlay Direct unusable, since the program that starts it resides in MBR and was overwritten by LILO. I found two ways to make it work:

1) The simple way
This will also work on systems with just one Hard drive (provided the QP Direct partition is in place). Two things must be done in Linux. First, use fdisk to change the QP Direct's type from D7 to 07 (zero seven): fdisk /dev/hda. In Fdisk's menu, 'p' prints the partition table. Use 't' to change the type and 'w' to write the changes to the partition table. Note that this will make the QP partition visible in Windows, since the MBR program no longer automagically changes it back upon booting. The second thing to do is to add an entry for Quick Play Direct in the LILO boot menu. Editing /etc/lilo.conf you can just copy the regular XP entry and change the partition number and boot menu name for the entry. That's all and it makes it possible to boot QuickPlay from the menu (but pressing the QP buttons on the computer will not work for direct access to QP). I use LILO, but the same thing can be done with GRUB as far as I see.

2) The complicated but more fulfilling way
To make the QP buttons on the keyboard work, we need to have the QP MBR program present. But LILO the Linux boot-loader usually also resides there. The solution is that LILO does not need to reside in the MBR, but can be installed in the Linux root drive's boot sector. If Linux is installed in the primary hard disk (for example in a 1 HDD-system), just making sure that the Linux installer writes the boot loader on the boot sector, not the MBR should keep everything working straight out of the box (I haven't tested this).

What's complicated is if Linux resides in the secondary hard disk. To make that work, we need to do a number of things. In short, to access the Linux system, a Linux entry is added into the Windows XP boot menu. The LILO -M option is used to create an MBR for the secondary disk, which will boot from the boot sector of the first active partition on the secondary HDD. The MBR is actually copied into the file that the Linux boot entry points to. I used the following excellent instructions to achieve this:

http://highlandsun.com/hyc/linuxboot.html

Note: if the root partition is an extended partition, for example /dev/hdb5, the keyword ext needs to be added to LILO's -M option (see the LILO man page).

At this point, I had LILO BOTH in the MBR and in the Linux root partition of the secondary HDD. Now, to make QPD work, I installed the QP Direct MBR by issuing the command 'mbrinst.exe /ini mbr.ini' from the QP Direct partition in WinXP (I had made the drive visible by changing its type from D7 to 07 with fdisk in Linux). This brought up a menu with some nice options, I left everything at default values, although for example the Stealth options seem to imply that the type-switching, which hides the QPD partition, can be disabled. It worked like a charm. The result is a boot with two menu levels: first the Windows XP boot menu, then, if Linux entry is chosen from that menu, the LILO menu with options for booting Linux (or back to Windows again...). The QP Direct buttons work as they shold, booting straight into Windows XP Embedded/Quickplay.

Note: when fiddling around with the MBR, keep a rescue disk handy so you can go boot your system and change things back if something goes wrong.

I hope this information is of some use to you. Also, I have a question: has anyone tried installing both QP 1.x and QP Direct 2.x on the same computer? I downloaded the files for QP 1.x here, but haven't tried the installation yet - I am not even sure if it supports my system. So, what are the caveats of having both QPs on the same system?

Great work linusl!

I have'nt been checking lately and come back to see that someone has made some progress. Anways, to answer your question, yes I have QP1 and QP2 on the same machine (DV1350 or something like that). It probably will NOT work on your machine, and here's why (going from memory, so bear with me):

For QP1.x, on a default DV1xxx machine, pressing a QP key to start results in the Bios looking for a Linux type 88 partition in the 2nd slot of the partition table. If found, it jumps to (somewhere within) what appears to be a GRUB stage 1.5 loader that is embedded in the boot sector of that partition. Note that it does not jump to the start of that sector, since that is non-executable code in the first 512+ bytes.

QP2.x, as you know, can be in any partition and the MBR code just swaps those type codes around to have it think it is THE boot partition. In fact, it will not start unless it is the primary boot partition since the WinPE environment is coded that way. Pressing a QP key on a machine with a Bios that supports QP2.x results in a special key code being passed to the MBR code, so it can then do it's magic.

So, for QP1.x type machines, the QP keys can boot into the QP1.x environment, but getting into QP2.x environments requires sequentially pressing two keys (Power -> QP) and even then is not 100% consistent. In a QP2.x machine, like yours, I don't see how you would get an updated bios to even attempt to boot the QP1.x environment. So far I cannot find a consistent way of having the MBR code jump into the QP1.x environment either, since it has some GRUB assumptions that I've not located.

Hope this makes sense.