HAPPINESS is when 'No Audio Devices Are Found, etc Gone
Moderators: Bill Smith, Pilot
Well unless this is a blow by blow description of what you are going thru, you just answered your own problem.taflocks wrote:the contents of this file cannot be unpackked the executable you are attempting to run has been corrupted please obtain another copy of this file verify its integrity and try again
Re-download and you should be good to go.
- George -
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
-
maine-iac
- Dan isn't smart enough to hire me
- Posts: 347
- Joined: Tue Mar 25, 2008 10:41 am
- Location: GA
taflocks,bneuman wrote:Right click on My Computer and click on Properties. Next click on the Advanced tab. You should see a button near the botton called Environment Variables. Click on it and change the tmp and temp directories to C:\temp. Make sure you have a C:\temp directory first. Also write down or remember where the tmp and temp directories are so you change them back. Do this, commit and reboot. Now try installing DirectX from your C: drive.taflocks wrote:what is /where is temp temp?
If you are trying to download to the flash on your thin client, that most likely will not work. The file can not be unpacked because you are running out of memory. You need to use a USB jump drive or something like it to download to. Also, change the temp directories to the drive letter of that USB drive. You may have to do a commit after changing the temp directories path before you try to download again.
Skin this one Pilgrim!taflocks wrote:that was the re download
http://dc14.4shared.com/download/526070 ... 062408.exe
- George -
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
Did you use the down load path I provided. If that doesn't work I don't know what you are going to do or why it is always corrupt.taflocks wrote:i need a ****ing hammer!!!
The link I posted points to a file that I have test and it is definitely good.
- George -
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
-
bneuman
- Dan isn't smart enough to hire me
- Posts: 136
- Joined: Tue Jan 01, 2008 8:31 pm
- Location: Baldwinsville, NY
before inserting your MJtaflocks wrote:i think i got it loaded but how can i get it not to re doo itself to the new update? in laymans terms now.
download stable downgrade here (1.73.4153.2910) .... 1.73.4153.2910
then edit your hosts file...put this line in it: 0.0.0.0 upgrade.talk4free.com
commit
reboot
insert MJ
find the file you downloaded (1.73.4153.2910) double click on it and it will install
HolmanGT wrote:Skin this one Pilgrim!taflocks wrote:that was the re download
http://dc14.4shared.com/download/526070 ... 062408.exe
HolmanGT did you get a thin client running on the new upgrade yet? I have a 5710 with 2x512. The direct x had to be downloaded twice due to corrupt file. I'm not sure if the self extracting service pack directx gets intalled or perhaps you have to go to altiris and run it from there after extraction? I am still investigating. If anyone has got a thin client to work with the new update please advise where and what directX files need to be installed. Should they show up somewhere? How can one know if directx is actually installed? It shouldn't be this complicated. Oh well I have the mj running on the old desktop for now but I want to get the old thin client running soon. Thin clients rule for quiet/cool running!
801 area code Salt Lake City area
"If the phone rings and nobody hears it, does it make a sound?"
"If the phone rings and nobody hears it, does it make a sound?"
Not HolmanGT, but...cameraman wrote:HolmanGT wrote:Skin this one Pilgrim!taflocks wrote:that was the re download
http://dc14.4shared.com/download/526070 ... 062408.exe
HolmanGT did you get a thin client running on the new upgrade yet? I have a 5710 with 2x512. The direct x had to be downloaded twice due to corrupt file. I'm not sure if the self extracting service pack directx gets intalled or perhaps you have to go to altiris and run it from there after extraction? I am still investigating. If anyone has got a thin client to work with the new update please advise where and what directX files need to be installed. Should they show up somewhere? How can one know if directx is actually installed? It shouldn't be this complicated. Oh well I have the mj running on the old desktop for now but I want to get the old thin client running soon. Thin clients rule for quiet/cool running!
I'm not by my thin client right now, but a DirectX folder does get created, but I can't tell you just where right now. It does not work on my 5700, and the last I heard HolmanGT did not have it working on any of his thin clients.
I am not sure what is being said her anymore, maybe never did.lymon wrote:Not HolmanGT, but...cameraman wrote:
HolmanGT did you get a thin client running on the new upgrade yet? I have a 5710 with 2x512. The direct x had to be downloaded twice due to corrupt file. I'm not sure if the self extracting service pack directx gets intalled or perhaps you have to go to altiris and run it from there after extraction? I am still investigating. If anyone has got a thin client to work with the new update please advise where and what directX files need to be installed. Should they show up somewhere? How can one know if directx is actually installed? It shouldn't be this complicated. Oh well I have the mj running on the old desktop for now but I want to get the old thin client running soon. Thin clients rule for quiet/cool running!
I'm not by my thin client right now, but a DirectX folder does get created, but I can't tell you just where right now. It does not work on my 5700, and the last I heard HolmanGT did not have it working on any of his thin clients.
Anyway here is how to install DirectX or The Gospel according to HolmanGT.
Steps to success:
Reference: "D" is your thumb drive whatever letter it may be. Use your assignment, yours might be "F" or whatever. Just look in My Computer and it will tell you the drive letter of your thumb drive. In my case it is a pinkie drive because size really doesn't matter, I hope.
Do not fool with your Z drive (the system ram drive) it is not necessary. Just trust me on this. besides it is right out of the HP manual to do it the way I will explain in a moment.
01. Download the file I posted the link to.
02. Put it on a thumb drive. And on a computer that has zip capabilities unzip it to a folder called sp36531 in the root of your thumb drive.
03. Now put the thumb drive in your Thin Client.
04. Open your Thumb Drive and create a folder tree that looks like this: \Administrator\Local Settings in the root of the thumb drive
05. Right click on My Computer, then the advanced tab then click on the Environment Variables button at the bottom of the window.
06. You will see to two user variables in the of the window one called TEMP and one called TMP and both will have the path Z:\\Administrator\Local Settings
07. Select the first one called TEMP then select the button just below that says edit and change only the drive letter to "D" without the quotes (remember your system may not be "D").
08. Repeat step 7 for the variable called TMP and change it to "D" also.
09. Now OK your way out of the Environment Variables window.
10. Now OK your way out of the System Properties window.
11. Go to the start button and select run.
12. In the run window paste the following string without the quotes changing the "D" to whatever the thumb drive is on your system "D:\sp36531\RIPs\Add_DirectX_9.0C_B1.exe -S".
13. Please note that my "D" may be something else on your system it is whatever your thumb drive is and please notice the space then hyphen "S" on the end of the string. please don't leave this off it is vital. Yes I know a gazillion people have done it without the "-S" this is another trust me it is required. Again the "-S" is right out of the HP instructions.
14. Now hit the enter key and sit back for awhile the only way to know when the damn thing is thru installing is to watch the screens pop up and the light on the thumb drive if yours has one. When both items show now further activity give it a couple of minutes more and consider it done.
15. Now right click on the EWF icon ( the green lock by the clock) and select commit, when prompted to reboot now select YES.
When it comes back to the Windows Desk Top you have successfully installed DirectX. To verify that something was installed you will find a DirectX folder in the Program Files folder. If you don't see it that is because I am wrong about it creating a folder there. But don't get alarmed on a conventional XP system you will not see a folder in the Program Files folder either. It is a system utility and is scattered all over creation if you have a program like SIW (goodle fore it) it will tell you what version of directX you have on your system. It is not necessary to do all of the checking unless you are from Missouri.
If you follow this it is 99.9% sure that it installed and installed correctly so please don't get alarmed if you can't immediately verify its existence.
And Lymon is correct I have never been able to make this work, so at the moment my MJ is running just fine using the down grade to the previous update, which is also a suggested work-around from Ymax which makes me think they might already be working on this bug.
If anyone has the patience to wait another 24 hours we may get a fix from Ymax. I am currently having a Tech session with a guy named Richard and I believe he is a Ymax Engineer. I have sent him a dump file of my thin client with the new update installed and Richard and the rest of his Engineering wolf pack are going to examine it tomorrow. If they can't find anything that way they are going to remote access my machine and attempt to analyze the problem. No guarantees but some how I managed to capture their attention with this one and they sincerely seem interested in getting to the bottom of this problem. IMHO this is a very genuine effort on the top tear Engineering level to resolve this and I have even had comments like "we are really interested to see your dump file" and the fact that they volunteered to log onto my machine and work on it remotely ... well I am pretty damn impressed with the level of interest and commitment they have shown.
- George -
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
-
bneuman
- Dan isn't smart enough to hire me
- Posts: 136
- Joined: Tue Jan 01, 2008 8:31 pm
- Location: Baldwinsville, NY
Excellent Tutorial on installing DirectX on a thin client!
bill
Also great news...maybe turn desperation and frustration back to being fun.HolmanGT wrote:If anyone has the patience to wait another 24 hours we may get a fix from Ymax. I am currently having a Tech session with a guy named Richard and I believe he is a Ymax Engineer. I have sent him a dump file of my thin client with the new update installed and Richard and the rest of his Engineering wolf pack are going to examine it tomorrow. If they can't find anything that way they are going to remote access my machine and attempt to analyze the problem. No guarantees but some how I managed to capture their attention with this one and they sincerely seem interested in getting to the bottom of this problem. IMHO this is a very genuine effort on the top tear Engineering level to resolve this and I have even had comments like "we are really interested to see your dump file" and the fact that they volunteered to log onto my machine and work on it remotely ... well I am pretty damn impressed with the level of interest and commitment they have shown.
bill
START -> Run -> Type "dxdiag" and press enter. You'll get a screen that looks like:cameraman wrote:How can one know if directx is actually installed?

magicJack: HP T5710 TC - 1GB/512MB - XPe SP2 - DirectX v9.0C Rev. B
Broadband: BHN - Road Runner Turbo - 15Mb down/2Mb up
Router: Smoothwall Express v3.0
Broadband: BHN - Road Runner Turbo - 15Mb down/2Mb up
Router: Smoothwall Express v3.0
So am I still the only person who has the latest version running on a T5710? My machine must be some kind of fluke. I even re-built my machine from scratch last night on a brand new 1GB flash drive I got from Transcend. The new flash drive appears to be a lot faster than the Apacer module that HP shipped with the unit. I got MJ working (again with the latest MJ release) in about 1 hour - so I know I can duplicate the results.HolmanGT wrote:Lymon is correct I have never been able to make this work, so at the moment my MJ is running just fine using the down grade to the previous update, which is also a suggested work-around from Ymax which makes me think they might already be working on this bug.
magicJack: HP T5710 TC - 1GB/512MB - XPe SP2 - DirectX v9.0C Rev. B
Broadband: BHN - Road Runner Turbo - 15Mb down/2Mb up
Router: Smoothwall Express v3.0
Broadband: BHN - Road Runner Turbo - 15Mb down/2Mb up
Router: Smoothwall Express v3.0
-
bneuman
- Dan isn't smart enough to hire me
- Posts: 136
- Joined: Tue Jan 01, 2008 8:31 pm
- Location: Baldwinsville, NY
I have a t5700 1gb/512 running with the latest upgrade. I plan on seeing if I can duplicate my success with my first t5700 tonight on my second t5700. I'll post my results...get ready HolmanGT!Nytefire wrote:So am I still the only person who has the latest version running on a T5710? My machine must be some kind of fluke. I even re-built my machine from scratch last night on a brand new 1GB flash drive I got from Transcend. The new flash drive appears to be a lot faster than the Apacer module that HP shipped with the unit. I got MJ working (again with the latest MJ release) in about 1 hour - so I know I can duplicate the results.
bill
-
bneuman
- Dan isn't smart enough to hire me
- Posts: 136
- Joined: Tue Jan 01, 2008 8:31 pm
- Location: Baldwinsville, NY
What thin client do you have? t5700. t5710, t5720taflocks wrote:yes the directx just downloading your file great until i press finish then it says cant load courept
What is the config? ROM/RAM 192/256, 256/256, 512/256, 512/512 or other
So you have never been able to open the DirectX file?
Where are you downloading from? Maybe we can find another place....
Is this the file your trying to download? sp36531.exe
I just down loaded the sp36531.exe file, right click on your download and see if under properties its this size...16.5 MB (17,335,968 bytes)
The file is self extracting... if it says corrupt then its corrupt....why, could be many reasons.
What are you downloading to? flash drive? if yes, what size?
please answer the questions so we can help you better...
bill
What thin client do you have? t5700. t5710, t5720 t5720
What is the config? ROM/RAM 192/256, 256/256, 512/256, 512/512 or other 1 gig 16 meg
So you have never been able to open the DirectX file? never
Where are you downloading from? Maybe we can find another place.... from your file
Is this the file your trying to download? sp36531.exe yes
I just down loaded the sp36531.exe file, right click on your download and see if under properties its this size...16.5 MB (17,335,968 bytes)
The file is self extracting... if it says corrupt then its corrupt....why, could be many reasons.
What are you downloading to? flash drive? if yes, what size? 2 gig sandisk
please answer the questions so we can help you better... Very Happy
What is the config? ROM/RAM 192/256, 256/256, 512/256, 512/512 or other 1 gig 16 meg
So you have never been able to open the DirectX file? never
Where are you downloading from? Maybe we can find another place.... from your file
Is this the file your trying to download? sp36531.exe yes
I just down loaded the sp36531.exe file, right click on your download and see if under properties its this size...16.5 MB (17,335,968 bytes)
The file is self extracting... if it says corrupt then its corrupt....why, could be many reasons.
What are you downloading to? flash drive? if yes, what size? 2 gig sandisk
please answer the questions so we can help you better... Very Happy
that didint work let's try this*****
What thin client do you have? t5700. t5710, t5720********************************* t5720
What is the config? ROM/RAM 192/256, 256/256, 512/256, 512/512 or other ************1 gig 16 meg
So you have never been able to open the DirectX file?******************************** never
Where are you downloading from? Maybe we can find another place...********************. from your file
Is this the file your trying to download? sp36531.exe ****************************************yes
I just down loaded the sp36531.exe file, right click on your download and see if under properties its this size...16.5 MB (17,335,968 bytes)
The file is self extracting... if it says corrupt then its corrupt....why, could be many reasons.
What are you downloading to? flash drive? if yes, what size? **********************************2 gig sandisk
please answer the questions so we can help you better... Very Happy
What thin client do you have? t5700. t5710, t5720********************************* t5720
What is the config? ROM/RAM 192/256, 256/256, 512/256, 512/512 or other ************1 gig 16 meg
So you have never been able to open the DirectX file?******************************** never
Where are you downloading from? Maybe we can find another place...********************. from your file
Is this the file your trying to download? sp36531.exe ****************************************yes
I just down loaded the sp36531.exe file, right click on your download and see if under properties its this size...16.5 MB (17,335,968 bytes)
The file is self extracting... if it says corrupt then its corrupt....why, could be many reasons.
What are you downloading to? flash drive? if yes, what size? **********************************2 gig sandisk
please answer the questions so we can help you better... Very Happy
-
mozerd
- MagicJack Contributor
- Posts: 52
- Joined: Thu Jun 05, 2008 11:22 am
- Location: Nepean ON Canada
- Contact:
Your Thin Client requires a minimum of 512MB of Flash ROM and a minimum of 512MB of RAM .... unless you have the minimums ROM and RAM DirectX will not install.taflocks wrote:What is the config? ROM/RAM 192/256, 256/256, 512/256, 512/512 or other ************1 gig 16 meg
In your response you states 1 gig 16 meg -- sorry but that makes no sense insofar as the ROM/RAM is concerned. You need to find out how much RAM you have and How much ROM you have. I currently do not remember where in Device Manger you could check to find out that info. [edit] sorry but device manger will not give you that info. You need to check the BIOS to get that info.
David Mozer
IT-Expert on Call
Information Technology for Home and Business
IT-Expert on Call
Information Technology for Home and Business
click on start right click on my computer/properties then it will tell you rom/ram .
that 16meg you are talking about goto your control panel click on ramdisk manager and increase your ram from 16 to say 24meg commit reboot.
that directx file does get corrupt sometimes it has happened to me also i just persisted and i finally was able to download a working version.
so am sure he is doing everything right just running into a bad file.
that 16meg you are talking about goto your control panel click on ramdisk manager and increase your ram from 16 to say 24meg commit reboot.
that directx file does get corrupt sometimes it has happened to me also i just persisted and i finally was able to download a working version.
so am sure he is doing everything right just running into a bad file.
Nytefire, now your rubbing salt in the wounds!Nytefire wrote:So am I still the only person who has the latest version running on a T5710? My machine must be some kind of fluke. I even re-built my machine from scratch last night on a brand new 1GB flash drive I got from Transcend. The new flash drive appears to be a lot faster than the Apacer module that HP shipped with the unit. I got MJ working (again with the latest MJ release) in about 1 hour - so I know I can duplicate the results.HolmanGT wrote:Lymon is correct I have never been able to make this work, so at the moment my MJ is running just fine using the down grade to the previous update, which is also a suggested work-around from Ymax which makes me think they might already be working on this bug.
The version you are using is the one from the HP site?
I also got the official word from MJ that DirectX is a required component!
- George -
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
Once we get yours working, I'll send you a Margarita to go with all of the salt.HolmanGT wrote:Nytefire, now your rubbing salt in the wounds!![]()
The version you are using is the one from the HP site?
I also got the official word from MJ that DirectX is a required component!
Everything I installed / uninstalled was from the HP site - except for magicJack and the java update required to run magic fix via IE*. For my T5710, I got the DirectX from this post.
Ok, good, that confirms what we've already known!
*I didn't install the java update and run magicfix until after I had my magicJack working.
Edit: Added link to DirectX post.
Last edited by Nytefire on Wed Jun 25, 2008 1:21 pm, edited 1 time in total.
magicJack: HP T5710 TC - 1GB/512MB - XPe SP2 - DirectX v9.0C Rev. B
Broadband: BHN - Road Runner Turbo - 15Mb down/2Mb up
Router: Smoothwall Express v3.0
Broadband: BHN - Road Runner Turbo - 15Mb down/2Mb up
Router: Smoothwall Express v3.0
Nytefire,Nytefire wrote:Once we get yours working, I'll send you a Margarita to go with all of the salt.HolmanGT wrote:Nytefire, now your rubbing salt in the wounds!![]()
The version you are using is the one from the HP site?
I also got the official word from MJ that DirectX is a required component!
Everything I installed / uninstalled was from the HP site - except for magicJack and the java update required to run magic fix via IE*.
Ok, good, that confirms what we've already known!
*I didn't install the java update and run magicfix until after I had my magicJack working.
To tell you the truth I was starting to get suspicious of the DirectX thing so I am very glad that I heard it from the horses mouth - no offense to you or the MagicJack guy that told me.
- George -
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
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.
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.
- George -
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
Edit - removed a double post.
Last edited by HolmanGT on Wed Jun 25, 2008 8:53 pm, edited 1 time in total.
- George -
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
HolmanGT - St. George, UT MJ-Area/Prefix 435-275
ooma-Area/Prefix 435-579
Baja Broadband, up-1mb dn-10mb, on days with a good tail wind.
MJ on HP T5730 2GBF/2GBR Thin Client XPe SP2 Router Dlink Dir-655
I think I accidently fixed mine too.... I was in the DirectX dialog box and tested the audio..... I then comitted and then removed the 0.0.00 Talk dada in my host file....comitted and everything is working fine.
But I don't know if I'm now using the latest update.....I just know my MJ is not trying to update.
How do I check the update version....?
Thanks, Mike
But I don't know if I'm now using the latest update.....I just know my MJ is not trying to update.
How do I check the update version....?
Thanks, Mike
-
bneuman
- Dan isn't smart enough to hire me
- Posts: 136
- Joined: Tue Jan 01, 2008 8:31 pm
- Location: Baldwinsville, NY
Right Click on Start/Explore/C:\Documents and Settings\Application Data\mjusbsp\dims24 wrote:I think I accidently fixed mine too.... I was in the DirectX dialog box and tested the audio..... I then comitted and then removed the 0.0.00 Talk dada in my host file....comitted and everything is working fine.
But I don't know if I'm now using the latest update.....I just know my MJ is not trying to update.
How do I check the update version....?
Thanks, Mike
right click on magicjack.exe
click on properties
click on version tab
you should see: file version: 1.80.441.1 if your running the latest
-
bneuman
- Dan isn't smart enough to hire me
- Posts: 136
- Joined: Tue Jan 01, 2008 8:31 pm
- Location: Baldwinsville, NY
Yeah it's recommended to start from scratch.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
from stroths
Reflashing with the Latest Xpe Operating System
1) Download onto your desktop computer HP’s XPe factory image for T5710 (was SP36064.exe at the time of this writing). For the t5700 sp29705.exe For the
t5720 sp39140.exe
2) Connect your USB disk-on-key (DOK) (I used a 2Gb “Kingston Data Travler R101”) to a USB port on your desktop computer.
3) Execute the file you just downloaded somewhere on your desktop system and when it asks select “USB Format” and your USB DOK as the destination.
4) Restart your TC and during power up press F10 to enter the bios settings.
5) Select USB as the first boot device and save the bios settings.
6) Power down the TC.
7) Insert the DOK into any USB port on the TC.
At this point the TC should go through a power up sequence and eventually begin to flash it’s internal memory from the data contained on the DOK. Be patient this takes quite a while to perform.
After the re-flash has completed you will be prompted to remove the DOK and cycle the power on the TC. I recommend at this point you during boot up you press F10 and change the bios back to so the first boot device is the ATA. Then save the bios setting and allow the TC to continue to boot. Once you have done that the TC should boot up into XP embedded and perform an auto logon into the “User” account.
Gaining Administrator Access
1) To gain access to the Administrator account so you can make changes you’ll need to hold down the shift key and go to the Start button and select log off. Keep the shift key depressed and the TC will then present you with a normal log on box.
2) In this logon box enter Administrator as both user and password. The TC will then log in as Administrator.
3) Next go into control panel and go to the "HP Login Manager". Change the Default User Name to Administrator and the Default User Password to Administrator as well. Just leave the Default Domain blank for now and click OK.
4) Now go to the EWF Configuration in control panel and select “Commit Data to Volume”. This will make the changes to logon on as Administrator persist; otherwise if you just rebooted the TC would revert to the setting you had at the last boot up. This is what EWF is all about. Any changes you make are just temporary when EWF is running and do not get permanently entered into the c: flash drive’s data unless you instruct EWF to do so by committing data to the volume.
Ok so we have now set the TC to auto logon as Administrator and made the settings permanent. Now you can go to the start button and select restart. The TC should restart and log back on as Administrator automatically.
Last edited by bneuman on Wed Jun 25, 2008 5:49 pm, edited 2 times in total.
