*HP HDX 9000 DRAGON Owners Lounge, Part 2*

[DRAGONe]

Thanks for your help and prodding to move onto Win 7 everyone.

Here comes the lightning stick again ... you need to swap your CPU; think like Mike, just do it!

[DRAGONe]

Too bad. Thanks for answering.

[L]

Let me qualify my reply, not without a massive engineering project to script the code it isn't.

[2.0™]

On booting from eSATA. Of course Dragon's right.

Though it can likely be done using a grub boot loader. I'm able to boot off the second internal drive using grub on a USB key. I did a write up in the old thread on how to do that. It likely just needs a small mod to access the eSATA.

Of note; when you run Acronis from USB key or CD/DVD, it can see the eSATA drive. So that leads me to believe a grub bootloader can too.

If I get time, I'll test it out.

[2.0™]

Happy Thanksgiving to all.

I can say I'm thankful for all of you - each of you made Dragon ownership a great experience. Wouldn't have been the same without you.

[User Retired 2]

Though it can likely be done using a grub boot loader. I'm able to boot off the second internal drive using grub on a USB key. I did a write up in the old thread on how to do that. It likely just needs a small mod to access the eSATA.

if the eSATA drive presents itself but there is no redirection option in BIOS, then can just use EasyBCD to add a new bootitem entry to your boot BCD to point to the 'eSATA' HDD for boot.

Happy Thanksgiving to all.

And Happy Thanksgiving to you too. Must be good to be back

[MobileArtist]

Happy Thanksgiving to all, and a more general salutation to all those not from the US.

Now just one question. Is stuffing whitelisted for the mpcie slot?

[RickiBerlin]

if the eSATA drive presents itself but there is no redirection option in BIOS, then can just use EasyBCD to add a new bootitem entry to your boot BCD to point to the 'eSATA' HDD for boot.

Exactly! And there are always the same old questions were already answered.

See my answer to "Black Knight" in October 2011, not two months old. This is naturally true for e-SATA.

Who "" EasyBCD is too complicated ......

There is also the possibility of a "system partition cloning" from Bay 1 to Bay 2, or e-SATA.
In this case, the MBR of Bay 1 is extended automatically. (Depends on settings)

[RickiBerlin]

Very smart approach. How are you doing this? Are you manually controlling the fan while bringing the gpu up to full load, and maximum temperature, and then while cooling down?

This also I have already described several times.

It is like a car in winter. One should to "the beginning of the trip" is not equal 200KM / h speed (124.27 mph). Can be better slowly warm.

My "GPU" is preheated before heavy load. There are many methods. (As in a car)
I use but no hair dryer.
I lift the "frequency" slow. (No load/no Game)
Only when I reach 60 ° C, the burden then GPU.
At the "cool" I'll leave the "frequency" high. (No load/no Game)
Only after some time I go in small steps up to 200MHz.

Because our fans are only indirectly controlled, in addition, I use "HWMonitor".
I'll explain again but not now. It is also not recommended to get from me.
Moreover, it is not necessary. For me, it only serves the noise reduction.
Only the "HWMonitor" "Ini Settings". Also important for "SetPll" usage.
The exact "temperature fan behavior" with "HWMonitor" I had described several times in other posts. Find exactly none.
Search to "NBR" is really a disaster.

And since my translations are always unintelligible , here's an example in figures.

I feel like gaming. By "10 clock" I turn my "HDX" one. (GPU to restart 35 ° C)
After 5 minutes in idle GPU already at 43 ° C.
Now I set the frequency to "383MHz at 0.9 V". (GPU goes up to about 53 ° C)
After 5 minutes (I cooked me a coffee) I set the GPU frequency to "at 500MHZ 1V"
Again, this setting I leave for 5 minutes. GPU temperature is then about 65 ° C.
Now (10.20 clock) I can start my game. It took me 20 minutes of my life.

Please remember this is just an example! The step with "383MHz" could be omitted.
Also, the temperature values ​​are only examples. These are of course influenced by the fan control.

I would have immediately started the game, then would the temperature within 2-3 minutes at 70-80 ° C. (Depending on the graphics requirements of the game)
And that's where I see the danger.

On cooling the reverse order!

The waiting time is always useful. Take a rag and cleanse your "HDX"!

If the GPU death then 3 hour repair time and costs about $ 150.

Instructions only available with "Powermizer off" (with the help of NVPMM) and "nvidia inspector".
If "Powermizer on" must be preheated in a different way. For example, with "YouTube video" or something similar. Thus can also be cooled slowly.

"@ 2.0"

The "GPU" is the temperature could not care less. Whether 30°C or 100°C degrees is not important.
Only the time of the variation within the recommended temperature range is critical. Even the "GPU" Throttelt the reach of "Tj.Max".
Therefore plays no major role in the overclocking. The "Nvidia chip" works well even with 182 ° C. See here a picture of a repair carried out by my GPU.
182 ° C at full load without any cooling system. At the frequency (275MHz) you realize this throttling.

If I "Dominick7" then I would just make this repair attempt.
Simply place a matchstick stuck in the "GPU Fan" fan and block it. Then run run "HDX" and "GPU" hot can. There is no danger for the rest of the "HDX".
Perhaps this has to be tried several times and does not help long term. But it would be a possibility without the "HDX" disassembly.

[RickiBerlin]

Ricki that information is DMI related and can be updated with HP DMI tools to any value you want

I too originally had problems with recovery disks for the HDX Dragon after replacing the motherboard of my machine.
Certain DMI information was missing in the BIOS and my Dragon was identified as a 8510X in computer properties.
Editing the DMI information in the BIOS was relatively straightforward with a program listed as HPBI103.EXE which allows edit of all the key DMI fields in the BIOS.
This program needs to be run in DOS with a bootable CD/Flash drive.
After populating the missing DMI info the recovery disks function perfectly and I was able to restore the machine to factory defaults.

What worked for me was to populate the 'Notebook Model' field with (HP Pavilion HDX9200 Notebook PC).
Recovery media does not work as I believe it is specifically looking for the HP and Pavilion entries in the NB model field to validate the install against the hardware.
My recovery media would also fail near the end of the recovery process with a cryptic error giving no clues as to what the problem was.
Using HPBI103.EXE to populate the Notebook Model in DMI using a bootable DOS image was what worked for me and restored the factory image including recovery partition.
Please remember to use the " characters when entering spaces in DOS i.e "HP Pavilion HDX9200 Notebook PC" and not struggle for days like myself wondering why I could not input this particular field properly.

I had never really thanked. Today there are + Rep.

Such as "DRAGON" already wrote (addressed to "ikilledbambi):

An excellent entrance into the forum sir.

I agree with him.
In the meantime, I had all my "HP DMI Tools" concerned. Besides "HPBI103.EXE" these are still a few more. see here:



What are all I know, unfortunately, not yet.
I think some are better for the activation of "Quad" on PM965. just kidding!

Whether there really a connection between the lack of "Bios Information" and "WiFi N6300 Ultimate" There remains a pure conjecture by me. (Presumption in this post)

What do you two think about it?

[MobileArtist]

As a simpler approach to "warming up the engine", would it be enough to start the Dragon, then after 10 minutes or so watch some video such as YouTube for another 10 or 20 minutes, and then after a bit move on to a game? Then, after the game, one would simply reverse the order from the graphics intensive game, to some less demanding video, and then to idle, and finally to shut down?

By the way, RickiBerlin, all of us appreciate the tremendous amount of work, and voluminous posts that you do for this forum. It is all the more appreciated, given that you are dealing with the language issue. Forgive me if I've asked a question that you've already answered. It's easy to miss some of that information, if one is not as technically adept as you and numerous others on this forum.

Danke!