Page 3 of 4
Posted: Wed Jun 25, 2008 5:38 pm
by lymon
taflocks wrote:was i supposed to? i have the new image and the directx on my pen drive 2 gig but how do i get it to flash? i cant even get in with a f8 command
Yes, you need to download the latest XPe image for the 5720 from HP's web site to your pen drive and reflash your 5720 with this image before you do anything else, then comes the DirectX and MJ stuff.
There are instructions for reflashing the XPe image somewhere in the thin client threads, I csn't recall all of the details, but it's pretty straight forward. Good luck.
Posted: Wed Jun 25, 2008 6:16 pm
by taflocks
gonna send her back to hp for a reflash and a fix no way i can get it to work all i get is the hp invent screen and when i go to f8 i get no where
Posted: Wed Jun 25, 2008 6:20 pm
by bneuman
taflocks wrote:gonna send her back to hp for a reflash and a fix no way i can get it to work all i get is the hp invent screen and when i go to f8 i get no where
when you powered back up did you keep hitting
F10 to get into the BIOS?
Did you buy the t5720 from a store or did you get it off ebay?
HP going to charge you to re-install the image?
bill
Posted: Wed Jun 25, 2008 6:29 pm
by taflocks
e bay but it has a warrenty until 2010 i have it set for usb boot but nothing happens i get hp screen black then a hp screen again
Posted: Wed Jun 25, 2008 6:57 pm
by dims24
Thanks guys!
My MJ is working better than ever with the new update....
Funny how simple it was to fix when you think about it:-)
Mike
Posted: Wed Jun 25, 2008 7:01 pm
by bneuman
taflocks wrote:e bay but it has a warrenty until 2010 i have it set for usb boot but nothing happens i get hp screen black then a hp screen again
yeah send it back if you have a warranty. good luck. after you get it back come on back if you need help.
bill
Posted: Wed Jun 25, 2008 7:39 pm
by lymon
Whack, just really whack--I don't understand why that made a difference, but my 5700 is updated and working too. HolmanGT, thanks for corralling that MJ engineer and forcing the solution out of him
My money had been riding on MJ doing it intentionally to force the thin clients out of the picture, live and learn...
Posted: Wed Jun 25, 2008 9:31 pm
by kconaty
So do I need to install DirectX or just go to the solution that HolmanGT outlined above?
Posted: Wed Jun 25, 2008 9:35 pm
by taflocks
was this rickard bone that was helping us out? he has been haaving a heck of a time trying to figure out why my mac will not m/j dial properly. i think it may be a usb voltage problem/
Posted: Wed Jun 25, 2008 10:41 pm
by lymon
kconaty wrote:So do I need to install DirectX or just go to the solution that HolmanGT outlined above?
If you mean the solution that involves running dxdiag, then yes, you need to install DirectX first. Dxdiag does not exist outside of a DirectX installation.
HolmanGT also describes how to install DirectX a few pages back. So, install DirectX first, then run dxdiag to fix issues with DirectX.
Posted: Thu Jun 26, 2008 2:17 am
by cameraman
HolmanGT wrote:Edit - removed a double post.
Double Kudos for your hard work HolmanGT, as well as the others who worked to fix this wacko problem. It is just after midnight and I read the post about dxdiag and just like "magic" the T5710 512/512 is back on the air again and running the latest version to boot! Now I don't have to listen to the noise of the fan on the old desktop 24/7. Thanks for pegging the fun meter!!!!!!!!!!!!!
Posted: Thu Jun 26, 2008 2:19 am
by cameraman
HolmanGT wrote:Edit - removed a double post.
The server is so slow I double posted his double post
Posted: Thu Jun 26, 2008 5:03 pm
by jrd4849
Hi guys. As a noob I have been watching this thread closely. After seeing all of the hoops that you guys had to jump through to get the update working I'm just wondering if it all was worth it. My MJ works pretty good on my t5710 with the old software. Are there some new developments in the latest upgrade that would pressure me to update? I guess I just have the "if it ain't broke..." attitude and am undecided about taking the plunge.
Jim
Posted: Thu Jun 26, 2008 5:22 pm
by HolmanGT
jrd4849 wrote:Hi guys. As a noob I have been watching this thread closely. After seeing all of the hoops that you guys had to jump through to get the update working I'm just wondering if it all was worth it. My MJ works pretty good on my t5710 with the old software. Are there some new developments in the latest upgrade that would pressure me to update? I guess I just have the "if it ain't broke..." attitude and am undecided about taking the plunge.
Jim
jrd,
I am sure there are some improvements with the new update, but I honestly couldn't tell you what they are from a users perspective.
I am pretty sure it has to do with using DirectX and the use of a more efficient codec. So it could be mostly in MJ's favor, the end user or both. And you might not see the improvements as an end user until your are subjected to some adverse conditions. Those being a slower than normal Network connection, a little busier computer than normal (yours of course).
Hell I am just guessing, for me I have not seen any difference.
But keep your pants on because I know that MagicJack Engineering is working on an update that will not require you to jump thru hoops, but it will require DirectX.
Regards,
Posted: Thu Jun 26, 2008 5:24 pm
by bneuman
jrd4849 wrote:Hi guys. As a noob I have been watching this thread closely. After seeing all of the hoops that you guys had to jump through to get the update working I'm just wondering if it all was worth it. My MJ works pretty good on my t5710 with the old software. Are there some new developments in the latest upgrade that would pressure me to update? I guess I just have the "if it ain't broke..." attitude and am undecided about taking the plunge.
Jim
I'm not really sure what the new update does, my MJ's work well either way. Don't let the 7 or 8 pages of this thread scare you. It all boils down to this:
you should (or need) at least 512/512
Install DirectX
Run DXDiag
Run the audio tests
upgrade to new version
You have to know how to download, install and commit changes....
bill
Posted: Thu Jun 26, 2008 11:02 pm
by maine-iac
So, does the Directx for the 5710 work on the 5700 or am I out of luck?
Posted: Thu Jun 26, 2008 11:22 pm
by lymon
maine-iac wrote:So, does the Directx for the 5710 work on the 5700 or am I out of luck?
I believe that you are in luck. DirectX and the dxdiag fix worked just fine on my 5700. In fact there are some release notes in one of the DirectX folders that indicate that DirectX is for the entire T5000 series.
Give it a go, and don't forget to commit.
Posted: Fri Jun 27, 2008 7:20 am
by Nytefire
bneuman wrote:jrd4849 wrote:Hi guys. As a noob I have been watching this thread closely. After seeing all of the hoops that you guys had to jump through to get the update working I'm just wondering if it all was worth it. My MJ works pretty good on my t5710 with the old software. Are there some new developments in the latest upgrade that would pressure me to update? I guess I just have the "if it ain't broke..." attitude and am undecided about taking the plunge.
Jim
I'm not really sure what the new update does, my MJ's work well either way. Don't let the 7 or 8 pages of this thread scare you. It all boils down to this:
you should (or need) at least 512/512
Install DirectX
Run DXDiag
Run the audio tests
upgrade to new version
You have to know how to download, install and commit changes....
bill
I would add:
Update audio device drivers [if needed]
Only because in addition to your steps, I had to do that on my T5710 to finally get it working. The reason I know this is because both times I installed DX I ran dxdiag to make sure it was installed properly and that the devices were working, however, my MJ didn't work until I updated the sound device drivers...
But hey, wtf do I know.
Posted: Fri Jun 27, 2008 8:05 am
by bneuman
Nytefire wrote:I would add:
Update audio device drivers [if needed]
Only because in addition to your steps, I had to do that on my T5710 to finally get it working. The reason I know this is because both times I installed DX I ran dxdiag to make sure it was installed properly and that the devices were working, however, my MJ didn't work until I updated the sound device drivers...
But hey, wtf do I know.
Good point...I haven't run into that issue on either of the t5700's I setup.
bill
Posted: Fri Jun 27, 2008 8:25 am
by mozerd
Its not at all clear to me if DirectX version 9.0C is actually required. DirectX is required that has been confirmed by HolmanGT but we do not know if MJ has a DirectX version 9.0C specific dependency.
Windows XP by default comes loaded with DirectX components - and it is very possible that the default version prior to 9.0C will work if the dxdiag utility is run. I cannot try that out because I have decommissioned my TC waiting for a flash memory upgrade to arrive. Perhaps someone who has a TC can try this out to see if after running the dxdiag diagnostic application on the default installed version of DirectX solves the problem.
Posted: Fri Jun 27, 2008 10:24 am
by Nytefire
Its not at all clear to me if DirectX version 9.0C is actually required. DirectX is required that has been confirmed by HolmanGT but we do not know if MJ has a DirectX version 9.0C specific dependency.
Seeing that 9.0c (revB) is all that's available from HP for the T5710 thin client - what other choice is there?
Posted: Fri Jun 27, 2008 11:22 am
by lymon
mozerd wrote:Its not at all clear to me if DirectX version 9.0C is actually required. DirectX is required that has been confirmed by HolmanGT but we do not know if MJ has a DirectX version 9.0C specific dependency.
Windows XP by default comes loaded with DirectX components - and it is very possible that the default version prior to 9.0C will work if the dxdiag utility is run. I cannot try that out because I have decommissioned my TC waiting for a flash memory upgrade to arrive. Perhaps someone who has a TC can try this out to see if after running the dxdiag diagnostic application on the default installed version of DirectX solves the problem.
On my 5700, dxdiag was not available until I installed 9.0C. I do not know if there were other components of DirectX present, but dxdiag was not there.
Posted: Fri Jun 27, 2008 11:29 am
by mozerd
Nytefire wrote:Its not at all clear to me if DirectX version 9.0C is actually required. DirectX is required that has been confirmed by HolmanGT but we do not know if MJ has a DirectX version 9.0C specific dependency.
Seeing that 9.0c (revB) is all that's available from HP for the T5710 thin client - what other choice is there?
As I stated earlier, Windows XP already has DirectX components installed by default -- not sure which version -- and I suspect that XPe also has the default version of DirectX resident .... why do I suspect that? All versions of magicJack software have a DirectX dependency based on my initial analysis. The latest magicJack update that caused everyone using a TC to fail may have included version 9.0C extensions which is why I initially suggested that people install the Altris DirectX update. It never dawned on me to suggest to run the dxdiag utility to fix DirectX corruption issues and so that is the reason that I suggested NOW for people to try working with the existing DEFAULT version of DirectX.
Also, many people using TC are removing many components and it is not at all clear to me if when doing so did the default version of DirectX get removed? If so then that would force people to install the Altris update for DirectX to get magicJack to work.
I hope this is clearer than mud.
Posted: Fri Jun 27, 2008 11:40 am
by mozerd
lymon wrote:On my 5700, dxdiag was not available until I installed 9.0C. I do not know if there were other components of DirectX present, but dxdiag was not there.
Thank you .... so based on the fact that the dxdiag utility is not present by default it is desirable to proceed with installing the 9.0C version of DirectX.
Posted: Fri Jun 27, 2008 11:46 am
by maine-iac
If someone has a freshly flashed T5700 before removing any programs can they verify that Dxdiag exists?
Posted: Fri Jun 27, 2008 12:01 pm
by lymon
maine-iac wrote:If someone has a freshly flashed T5700 before removing any programs can they verify that Dxdiag exists?
That is a very good question. In retrospect, I used stroths instant flash all in one version 1.1 to flash my 5700. So, it's entirely possible that stroths removed some items before creating the final image.
If no one else comes up with an answer, I may reflash mine with a fresh HP XPe image later and try the dxdiag test myself.
Posted: Fri Jun 27, 2008 12:18 pm
by bneuman
maine-iac wrote:If someone has a freshly flashed T5700 before removing any programs can they verify that Dxdiag exists?
I've been told that the original few release's of XPe for the t5700 did not have DirectX installed. So no DxDiag. Possibly a stripped down version maybe be in the latest release (256 min ram).
I also have stroths 1.1 on both of my t5700's. I never checked for DirectX when I first got mine.
bill
Posted: Fri Jun 27, 2008 1:09 pm
by Nytefire
mozerd wrote:Nytefire wrote:Seeing that 9.0c (revB) is all that's available from HP for the T5710 thin client - what other choice is there?
As I stated earlier, Windows XP already has DirectX components installed by default -- not sure which version -- and I suspect that XPe also has the default version of DirectX resident .... why do I suspect that? All versions of magicJack software have a DirectX dependency based on my initial analysis. The latest magicJack update that caused everyone using a TC to fail may have included version 9.0C extensions which is why I initially suggested that people install the Altris DirectX update. It never dawned on me to suggest to run the dxdiag utility to fix DirectX corruption issues and so that is the reason that I suggested NOW for people to try working with the existing DEFAULT version of DirectX.
Also, many people using TC are removing many components and it is not at all clear to me if when doing so did the default version of DirectX get removed? If so then that would force people to install the Altris update for DirectX to get magicJack to work.
I hope this is clearer than mud.
This thread was originally in reference to the HP Thin Clients which are running Windows XP Embedded - that was provided by HP. In the HP provided flash install there are no DirectX components provided.
Now for windows XP, sure I agree with you, but for the HP provided flash image, I don't.
Posted: Fri Jun 27, 2008 1:45 pm
by mozerd
Nytefire wrote:mozerd wrote:Nytefire wrote:Seeing that 9.0c (revB) is all that's available from HP for the T5710 thin client - what other choice is there?
As I stated earlier, Windows XP already has DirectX components installed by default -- not sure which version -- and I
suspect that XPe also has the default version of DirectX resident .... why do I suspect that? All versions of magicJack software have a DirectX dependency based on my initial analysis.
This thread was originally in reference to the HP Thin Clients which are running Windows XP Embedded - that was provided by HP. In the HP provided flash install there are no DirectX components provided.
Now for windows XP, sure I agree with you, but for the HP provided flash image, I don't.
I am delighted to read that you cannot read or comprehend my commentary. Thanks for the illumination.
[EDIT] Update: I have confirmation that the default XPe flash suppled by HP does have the DirectX components installed -- apparently you can confirm this by running an older version of magicJack and when you invoke magic FIX [from the magicJack website] it goes through a series of tests and reports on a host of stuff it finds
including DirectX --- a number of people have written to me stating that magicFIX places a green check mark besides DirectX [signifying the presence of DirtectX components] --- but no dxdiag application is available in the older version -- so apparently the latest magicJack upgrade application does have a DirectX v9.0C
dependency and Microsoft have also supplied DirectX diagnostic/repair utility called dxdiag due to the fact that many DirectX installs have corruption issues caused primarily by disk fragmentation and electrical issues
Posted: Fri Jun 27, 2008 2:36 pm
by Nytefire
Edited: Nevermind.
Posted: Sat Jun 28, 2008 5:38 pm
by Mark
HolmanGT wrote:Attention All
For those that have been following my saga or just trying to make their machine work with the new update as Mike and Bill were fortunate enough to make happen on their machines I believe I have an answer for every one that was in my boat.
Here is the solution provided to me by a gentleman by the name of Richard whom I believe is a MagicJack or Ymax engineer.
They analyzed some information from my machine then asked me to run the DirectX diagnostic and send them a report that it generates after you have gone thru all the diagnostic test. He also made a comment that just running the diagnostic may itself fix my problem.
Well running the diagnostic did fix my problem and I am now the very happy owner of a working T5710 512/512 running the newest update from MagicJack.
Here is all you have to do and it is not going to sound very technical or sophisticated but you can't complain about victory almost regardless of how you got there.
1. Plug in the magicJack device and wait until the softphone starts.
2. Go to the Windows Start menu, choose "Run...", enter "dxdiag", hit Enter. A window of dxdiag utility will appear.
3. Watch a progress bar (may be slow) in the lowermost left corner of the window. Wait until it disappears.
4. Go Thru some of the different diagnostic test. I think I tried ever thing that said test this or that.
5. Then when you are through just exit the program do a commit and when it restarts you will most likely be running the lasted MagicJack update successfully.
Told you it wouldn't sound technical enough to fix any thing but thank God it does. I personally feel like a new man.
I installed DirectX 9.0c according to HolmanGT's instructions on page 5 of this thread and also followed the above suggestion to run diagnostic tests and now I'm able to run the latest version of magicJack on my HP t5720 Thin Client.
Thank you HolmanGT and the magicJack programmer and/or the engineer you communicated with who gave you the suggestion to run the diagnostic tests. I now have a fully functioning magicJack on my t5720.
No more "no output/input devices are found" error message.
Posted: Sat Jun 28, 2008 9:20 pm
by HolmanGT
Mark,
Glad it worked for you. And they are coming out with an update "
Soon" that will make using the Diagnostic unnecessary. They loaned me a copy of the beta and it did work as they said it would so pretty soon that little nuisance will be a thing of the past.
Having your MJ down is almost as bad as having your Broad Band down.
Posted: Sun Jun 29, 2008 12:03 am
by baracca
Looks like most people have the HP thin clients. I am stuck with a neoware e140 and it has no directx snap-in download from HP. This thing is driving me nuts!
Posted: Sun Jun 29, 2008 1:27 am
by Mark
baracca wrote:Looks like most people have the HP thin clients. I am stuck with a neoware e140 and it has no directx snap-in download from HP. This thing is driving me nuts!
I'm not sure I understand your dilemma. The e140 looks like its equal to the t5720. If you're looking for the DirectX 9.0c embedded, can't you use the same version used for the t5720? If you have a USB stick (I bought a Sony 4GB from Wal-Mart) you should be able to follow the instructions to install it and get magicJack with latest software up and running--at least I would think so.
Posted: Sun Jun 29, 2008 12:37 pm
by HolmanGT
baracca wrote:Looks like most people have the HP thin clients. I am stuck with a neoware e140 and it has no directx snap-in download from HP. This thing is driving me nuts!
There is not one for the T5700 either but I use the one for the T5710 and it works fine. But you have to have 512/512 minimum on the memory or you will end up like I did yesterday. I fought it all day trying to make it work on 512/256 - it is impossible but it won't tell you that it just won't work.
Posted: Sun Jun 29, 2008 12:56 pm
by kconaty
ok, installed directx yesterday, mj worked fine. now today can receive calls but cannot call out. any ideas? Are MJ servers down? Nothing has changed since yesterday on my end
Posted: Sun Jun 29, 2008 1:44 pm
by lymon
kconaty wrote:ok, installed directx yesterday, mj worked fine. now today can receive calls but cannot call out. any ideas? Are MJ servers down? Nothing has changed since yesterday on my end
Dunno, mine is working. Did you commit after running dxdiag?
Posted: Sun Jun 29, 2008 1:57 pm
by kconaty
ya, like I said it was working fine yesterday
Posted: Sun Jun 29, 2008 3:52 pm
by HolmanGT
kconaty wrote:ya, like I said it was working fine yesterday
Just because it was working yesterday doesn't mean you did a commit. Wouldn't be the first time I thought I did a commit and discovered two day later when I did a power cycle that Oops - it is all gone.
Posted: Sun Jun 29, 2008 3:53 pm
by HolmanGT
kconaty wrote:ya, like I said it was working fine yesterday
Just because it was working yesterday doesn't mean you did a commit. Wouldn't be the first time I thought I did a commit and discovered two day later when I did a power cycle that Oops - it is all gone.
Posted: Sun Jun 29, 2008 6:14 pm
by kconaty
ya, I did a commit yesterday; again today
Posted: Sun Jun 29, 2008 8:21 pm
by kconaty
clicked on magicfix and it told me that I could not connect to the calling servers.
left it and came back hours later and now it is working.
Posted: Sun Jun 29, 2008 11:38 pm
by baracca
What instructions were you referring to? I don't have a server to install Altiris Deployment Server on. Any other way to try to install the t5720 version? You mentioned a USB stick, care to elaborate? Sorry for being a noob.
OK, just tried to extract and install the t5720 version of directx but it errored out. There is a VBScript error checking for SystemBiosVersion "hp t5700". Anyway around this?
Mark wrote:baracca wrote:Looks like most people have the HP thin clients. I am stuck with a neoware e140 and it has no directx snap-in download from HP. This thing is driving me nuts!
I'm not sure I understand your dilemma. The e140 looks like its equal to the t5720. If you're looking for the DirectX 9.0c embedded, can't you use the same version used for the t5720? If you have a USB stick (I bought a Sony 4GB from Wal-Mart) you should be able to follow the instructions to install it and get magicJack with latest software up and running--at least I would think so.
Posted: Mon Jun 30, 2008 12:23 am
by Mark
baracca wrote:What instructions were you referring to? I don't have a server to install Altiris Deployment Server on. Any other way to try to install the t5720 version? You mentioned a USB stick, care to elaborate? Sorry for being a noob.
OK, just tried to extract and install the t5720 version of directx but it errored out. There is a VBScript error checking for SystemBiosVersion "hp t5700". Anyway around this?
Mark wrote:baracca wrote:Looks like most people have the HP thin clients. I am stuck with a neoware e140 and it has no directx snap-in download from HP. This thing is driving me nuts!
I'm not sure I understand your dilemma. The e140 looks like its equal to the t5720. If you're looking for the DirectX 9.0c embedded, can't you use the same version used for the t5720? If you have a USB stick (I bought a Sony 4GB from Wal-Mart) you should be able to follow the instructions to install it and get magicJack with latest software up and running--at least I would think so.
I'm just trying to follow where you're having problems. Here is a link to Hewlett Packard's website and Neoware software and support:
http://h20000.www2.hp.com/bizsupport/Te ... g=en&cc=us
Notice the link to Windows XPe
Here is the actual XPe version for your Neoware:
http://h20000.www2.hp.com/bizsupport/Te ... vc-60031-1
If you have a working version of Windows XPe then go to page 5 of this thread and you will notice instructions for installing DirectX 9.0c. After installing DirectX follow the instructions for running diagnostic which I quoted in my previous link.
Posted: Mon Jun 30, 2008 2:59 am
by baracca
I followed the instructions on page 5 and still got the VBScript error mentioned below. There was a typo from my previous post, it was "hp t5000", not "hp t5700". I found the registry key in the e140 and tried changing the SystemBiosVersion to "hp 5000" to trick it into installing but that didn't work (same message). I guess it was working for the HP t5xxx series thin clients but nothing else. Thanks for trying to help.
Mark wrote:baracca wrote:What instructions were you referring to? I don't have a server to install Altiris Deployment Server on. Any other way to try to install the t5720 version? You mentioned a USB stick, care to elaborate? Sorry for being a noob.
OK, just tried to extract and install the t5720 version of directx but it errored out. There is a VBScript error checking for SystemBiosVersion "hp t5700". Anyway around this?
Mark wrote:
I'm not sure I understand your dilemma. The e140 looks like its equal to the t5720. If you're looking for the DirectX 9.0c embedded, can't you use the same version used for the t5720? If you have a USB stick (I bought a Sony 4GB from Wal-Mart) you should be able to follow the instructions to install it and get magicJack with latest software up and running--at least I would think so.
I'm just trying to follow where you're having problems. Here is a link to Hewlett Packard's website and Neoware software and support:
http://h20000.www2.hp.com/bizsupport/Te ... g=en&cc=us
Notice the link to Windows XPe
Here is the actual XPe version for your Neoware:
http://h20000.www2.hp.com/bizsupport/Te ... vc-60031-1
If you have a working version of Windows XPe then go to page 5 of this thread and you will notice instructions for installing DirectX 9.0c. After installing DirectX follow the instructions for running diagnostic which I quoted in my previous link.
jittery voice
Posted: Wed Jul 02, 2008 10:52 am
by larbell
Hi All:
Not sure if this is the right topic, but... I'm running an HP 5700 512/512 and I've got the directx running as directed. Everything works however...
I'm getting jittery voice and breakup on calls.
I already set to background settings, and I have a wired Linksys router so I don't have any of the wireless settings that were mentioned in other threads.
I'm running in a 917 area code, connecting to the HP it via xp remote connect, and I've uninstalled most everything that can be removed. I also have a copy of winpatrol, and I've stopped all services except the essentials.
Cpu use (which I can only see while remote connected) runs 5-10% when nothing is going on which appears split between taskmgr and remote connect svcs. When I make a call it runs between 50-75% with some spikes to 90-100% when I press phone keys for remote systems.
Any suggestions? I don't see a lot of posts of unresolved jittery voice, and it's really annoying.
Thanks
Re: jittery voice
Posted: Fri Jul 04, 2008 11:41 am
by mozerd
larbell wrote:Any suggestions? I don't see a lot of posts of unresolved jittery voice, and it's really annoying.Thanks
Control Panel
System
Advanced
Performance
Settings
Visual Effects
Adjust for best performance
Apply then OK then OK then COMMIT
On a Thin Client the above adjustment will help sound issues but other important considerations will also help to improve voice quality. If you're using
Team-Viewer for remote control of the TC -- a great little application -- but a real
resource hog that will
destroy the sound quality for magicJack on a Thin Client whose processor is
1Ghz or less - if your TC has a much faster processor then
Team-Viewer is less of an issue --- however I would not encourage anyone to use
Team-Viewer on a TC like the HP 5700 series with magicJack. DirectX v9.0C provides superior sound output for MJ and much less drag on the CPU however
Team-Viewer will obliterate any advantage that DirectX v9.0C provides based on my tests.
In conclusion - what is the sum of it all?
Posted: Fri Jul 04, 2008 4:16 pm
by jwryahoo
Wow - this is quite a thread of information. Some of it can be confusing.
I just wanteda to get a clear idea of what would required to get my TC 5710 512/256 up and running. Perhaps HolmanGT can confirm this.
1. According to HolmanGT's post/proceedure on page 5 -- the size of the ram doesn't matter using his method of installing DX 9 (mine is 512/256) . Is this correct?
2. Once DX9 is installed then you would just run the "dxdialog" and that should fix the "no audio" problem with MJ?
3. Am I missing anything else other than possiblly updating the audio drivers?
Thanks so much for all your help.
Blessings
jwr
Re: In conclusion - what is the sum of it all?
Posted: Fri Jul 04, 2008 4:34 pm
by HolmanGT
jwryahoo wrote:Wow - this is quite a thread of information. Some of it can be confusing.
I just wanteda to get a clear idea of what would required to get my TC 5710 512/256 up and running. Perhaps HolmanGT can confirm this.
1. According to HolmanGT's post/proceedure on page 5 -- the size of the ram doesn't matter using his method of installing DX 9 (mine is 512/256) . Is this correct?
2. Once DX9 is installed then you would just run the "dxdialog" and that should fix the "no audio" problem with MJ?
3. Am I missing anything else other than possiblly updating the audio drivers?
Thanks so much for all your help.
Blessings
jwr
HolmanGT lied about the 256 RAM and I don't know the post you are referring to but if I said that and I may well have. My self and Dave have discovered you must have 512/512 to rung the DirectX. I fought this for hours then compared notes with Dave stuck a 512 RAM module in and it just started working. So the correct answer as of 7-4-08 @ 14:32 MDT you have to have 512/512 or it will not work. Sorry if my post claiming 512/256 caused you a lot of trouble, but it is NOT correct.
Posted: Fri Jul 04, 2008 4:44 pm
by kulumbaa
i was successful in installing dx9 on a t5700 256/256..
the reason i installed in the 256/256 was due to sound distortions which hasnt gone away even after the dx9 install howver i dont have any no audio found. but its still useless because the sound is static and distorted when i put the phone on.
howver i was unable to duplicate the same on a t5710 256flash 512 ram will have to try again in the weekend but i think it can be done