new up-date #1.80.4992.3489
Moderators: Bill Smith, Pilot
new up-date #1.80.4992.3489
added manual select for cable /DSL or Wi-Fi settings & wireless card option
upgrade # 1.80.4992.3489
http://upgrades.magicjack.com/upgrade/upgrade.exe
upgrade # 1.80.4992.3489
http://upgrades.magicjack.com/upgrade/upgrade.exe
Last edited by Mimon on Fri Jul 31, 2009 3:05 pm, edited 1 time in total.
Re: new up-date #1.80.4992.3489
Mimon wrote:added manual select for cable /DSL or Wi-Fi settings & wireless card option
upgrade # 1.80.4992.3489
Well, it would be nice if they would put out a message that describes the fixes and/or updates.
I am most interested to see if the DTMF talk-off issue (i.e. beeping) is any better.
-Curt
--magicJack user since Oct 08 w/magicFeatures
--D-Link DIR-655
-NetTalk DUO since Dec 10
--magicJack user since Oct 08 w/magicFeatures
--D-Link DIR-655
-NetTalk DUO since Dec 10
-
AlaninKY
- Dan isn't smart enough to hire me
- Posts: 270
- Joined: Mon Nov 12, 2007 3:59 pm
- Location: Louisville, KY USA
- Contact:
Re: new up-date #1.80.4992.3489
All 4 of my Jacks, which are on separate computers, have been updated with the new upgrade. No issues with it yet.Mimon wrote:added manual select for cable /DSL or Wi-Fi settings & wireless card option
upgrade # 1.80.4992.3489
Re: new up-date #1.80.4992.3489
Please post the new upgrade link. Thanks.Mimon wrote:added manual select for cable /DSL or Wi-Fi settings & wireless card option
upgrade # 1.80.4992.3489
Re: new up-date #1.80.4992.3489
luigi2008 wrote:Please post the new upgrade link. Thanks.Mimon wrote:added manual select for cable /DSL or Wi-Fi settings & wireless card option
upgrade # 1.80.4992.3489
If you are running the stroth's utility, I just clicked 'upgrade magicJack software' and the upgrade started.
-Curt
--magicJack user since Oct 08 w/magicFeatures
--D-Link DIR-655
-NetTalk DUO since Dec 10
--magicJack user since Oct 08 w/magicFeatures
--D-Link DIR-655
-NetTalk DUO since Dec 10
- Robert121571
- magicJack Apprentice
- Posts: 20
- Joined: Sat Jun 27, 2009 1:40 am
I don't get the update
I have just tried several times to pull the new update even downloaded from the link posted above and even tried from magicjacks page. I don't get a new version. I even went as far as removing all the files from the laptop that I use as a server for magicjack and then let it reinstall still no new version.
Re: I don't get the update
Robert121571 wrote:I have just tried several times to pull the new update even downloaded from the link posted above and even tried from magicjacks page. I don't get a new version. I even went as far as removing all the files from the laptop that I use as a server for magicjack and then let it reinstall still no new version.
I read on one of the other discussion threads that there may be an issue with Vista and the upgrade, so perhaps they pulled it? Don't know, but it runs fine on XP.
Last edited by newtoncd on Fri Jul 31, 2009 8:31 pm, edited 2 times in total.
-Curt
--magicJack user since Oct 08 w/magicFeatures
--D-Link DIR-655
-NetTalk DUO since Dec 10
--magicJack user since Oct 08 w/magicFeatures
--D-Link DIR-655
-NetTalk DUO since Dec 10
-
xxxemofreakxxx
- magicJack Apprentice
- Posts: 26
- Joined: Fri Sep 12, 2008 1:20 pm
- Robert121571
- magicJack Apprentice
- Posts: 20
- Joined: Sat Jun 27, 2009 1:40 am
I don't know if its been pulled, however, I had it force feed to me this morning... Looks like its all working from my end... and as a bonus, seems the back ground beeping has gone away...Robert121571 wrote:I'm thinking it was pulled now as well. I've been reading another post that had a screen shot of it and I posted in there too that I think it was pulled. Since it seems that not many people are talking about it.
download
in case anyone might still want the(1.80.4992.3489) update,It is in a zip-folder under my email Addy ([email protected])
@ http://www.4shared.com/file/122125005/e ... 3489_.html
@ http://www.4shared.com/file/122125005/e ... 3489_.html
Last edited by Mimon on Sun Aug 02, 2009 5:00 pm, edited 1 time in total.
-
Popgory
- MagicJack Contributor
- Posts: 61
- Joined: Sat Apr 04, 2009 1:03 pm
- Location: Chicago, metro NW
On my TC, Win XPe SP2 ....AlaninKY wrote:The upgrade does appear to run fine on XP as all 4 of my computers and 4 Jacks run on various versions of XP
Performance same as B/4 (very, very good). Will place a call to myself after everyone gets up to test the previous registry modifications enabling the home answering machine. Will post if any issues.
Popgory
Wyse 9450xe TC, 1Gf/1Gr; XPe sp2, powered hub
Linksys BEFSX41, Hawking HBB1, Spedstrm 5100b
ADSL 5200 down / 650 up
Wyse 9450xe TC, 1Gf/1Gr; XPe sp2, powered hub
Linksys BEFSX41, Hawking HBB1, Spedstrm 5100b
ADSL 5200 down / 650 up
Yesterday my MJ (on TC5700, 256/256, XPe, SP2) stopped working. Rebooted and it worked for few hours then down again. Today, I connected remotely and realized that MJ was unable to restart after the new update. Started MJ it manually and it worked. Few hours later, same thing, MJ down. Disabled EWF (isnt this that enables/unables writing changes on "HDD"?). Now up and running since couple of hours. Will see. My question is this: do you need to disable EWF for the changes to be registered and keep it disabled thereafter for all future updates/upgrades?Popgory wrote:On my TC, Win XPe SP2 ....AlaninKY wrote:The upgrade does appear to run fine on XP as all 4 of my computers and 4 Jacks run on various versions of XP
Performance same as B/4 (very, very good). Will place a call to myself after everyone gets up to test the previous registry modifications enabling the home answering machine. Will post if any issues.
-
Popgory
- MagicJack Contributor
- Posts: 61
- Joined: Sat Apr 04, 2009 1:03 pm
- Location: Chicago, metro NW
stav wrote:Popgory wrote:Yes, EWF must be off for the changes to be written to the DOM (Disk on Memory).AlaninKY wrote:... Started MJ it manually and it worked. Few hours later, same thing, MJ down. Disabled EWF (isnt this that enables/unables writing changes on "HDD"?). Now up and running since couple of hours. Will see. My question is this: do you need to disable EWF for the changes to be registered and keep it disabled thereafter for all future updates/upgrades?
It is up to you as to whether or not you keep EWF enabled. EWF is there to lengthen the life of your DOM module. I use it. I also check the TC once in in the morning to see if it rebooted (due to a "pushed" update). If it has, I go thru the exercise manually (disable EWF, update, enable EWF). Ya, it is extra work but I want the control just in case a pushed update causes problems.
Popgory
Wyse 9450xe TC, 1Gf/1Gr; XPe sp2, powered hub
Linksys BEFSX41, Hawking HBB1, Spedstrm 5100b
ADSL 5200 down / 650 up
Wyse 9450xe TC, 1Gf/1Gr; XPe sp2, powered hub
Linksys BEFSX41, Hawking HBB1, Spedstrm 5100b
ADSL 5200 down / 650 up
Popgory wrote:stav wrote:Thanks for sharing,Popgory wrote: Yes, EWF must be off for the changes to be written to the DOM (Disk on Memory).
It is up to you as to whether or not you keep EWF enabled. EWF is there to lengthen the life of your DOM module. I use it. I also check the TC once in in the morning to see if it rebooted (due to a "pushed" update). If it has, I go thru the exercise manually (disable EWF, update, enable EWF). Ya, it is extra work but I want the control just in case a pushed update causes problems.
Can you expand on this "EWF is there to lengthen the life of your DOM module". Why is that?
-
bitstopjoe
- Future magicJack CEO
- Posts: 2844
- Joined: Sat Sep 13, 2008 5:25 pm
- Location: North East Pennsylvania
Aren't those cycles reversible, ie. counter goes back to zero with a reboot? If not that would mean that these flash memories have finite life and when the total cycles are met, they shut off? Am I getting this last point right? Thxbitstopjoe wrote:Because flash memory has a finite amount of read/write cycles. So less is more.
Joe Sica
-
bitstopjoe
- Future magicJack CEO
- Posts: 2844
- Joined: Sat Sep 13, 2008 5:25 pm
- Location: North East Pennsylvania
From Wikipedia:
Memory wear
Another limitation is that flash memory has a finite number of erase-write cycles. Most commercially available flash products are guaranteed to withstand around 100,000 write-erase-cycles, before the wear begins to deteriorate the integrity of the storage.[citation needed] The guaranteed cycle count may apply only to block zero (as is the case with TSOP NAND parts), or to all blocks (as in NOR). This effect is partially offset in some chip firmware or file system drivers by counting the writes and dynamically remapping blocks in order to spread write operations between sectors; this technique is called wear levelling. Another approach is to perform write verification and remapping to spare sectors in case of write failure, a technique called Bad Block Management (BBM). For portable consumer devices, these wearout management techniques typically extend the life of the flash memory beyond the life of the device itself, and some data loss may be acceptable in these applications. For high reliability data storage, however, it is not advisable to use flash memory that would have to go through a large number of programming cycles. This limitation is meaningless for 'read-only' applications such as thin clients and routers, which are only programmed once or at most a few times during their lifetime.
The last paragraph seems to point to TC being read only so in fact it may be a moot point to turn EWF off!! One learns something new every day!!!
COOL!
Joe Sica
Memory wear
Another limitation is that flash memory has a finite number of erase-write cycles. Most commercially available flash products are guaranteed to withstand around 100,000 write-erase-cycles, before the wear begins to deteriorate the integrity of the storage.[citation needed] The guaranteed cycle count may apply only to block zero (as is the case with TSOP NAND parts), or to all blocks (as in NOR). This effect is partially offset in some chip firmware or file system drivers by counting the writes and dynamically remapping blocks in order to spread write operations between sectors; this technique is called wear levelling. Another approach is to perform write verification and remapping to spare sectors in case of write failure, a technique called Bad Block Management (BBM). For portable consumer devices, these wearout management techniques typically extend the life of the flash memory beyond the life of the device itself, and some data loss may be acceptable in these applications. For high reliability data storage, however, it is not advisable to use flash memory that would have to go through a large number of programming cycles. This limitation is meaningless for 'read-only' applications such as thin clients and routers, which are only programmed once or at most a few times during their lifetime.
The last paragraph seems to point to TC being read only so in fact it may be a moot point to turn EWF off!! One learns something new every day!!!
COOL!
Joe Sica
Not sure how to read that,bitstopjoe wrote:From Wikipedia:
Memory wear
Another limitation is that flash memory has a finite number of erase-write cycles. Most commercially available flash products are guaranteed to withstand around 100,000 write-erase-cycles, before the wear begins to deteriorate the integrity of the storage.[citation needed] The guaranteed cycle count may apply only to block zero (as is the case with TSOP NAND parts), or to all blocks (as in NOR). This effect is partially offset in some chip firmware or file system drivers by counting the writes and dynamically remapping blocks in order to spread write operations between sectors; this technique is called wear levelling. Another approach is to perform write verification and remapping to spare sectors in case of write failure, a technique called Bad Block Management (BBM). For portable consumer devices, these wearout management techniques typically extend the life of the flash memory beyond the life of the device itself, and some data loss may be acceptable in these applications. For high reliability data storage, however, it is not advisable to use flash memory that would have to go through a large number of programming cycles. This limitation is meaningless for 'read-only' applications such as thin clients and routers, which are only programmed once or at most a few times during their lifetime.
The last paragraph seems to point to TC being read only so in fact it may be a moot point to turn EWF off!! One learns something new every day!!!
COOL!
Joe Sica
if TC is read only, then why even bother having EWF on the XPe? Also, when plugging in the MJ, there are files and scripts being written somewhere on the flash, right? By far not a IT specialist ... just thinking .. any ways, it looks like the MJ didnt like the new upgrade since I got a "Bad sector " warning on a red background on the dongle image.!! Then as I reported earlier, it seems to work fine that I disable the EWF so that the new update and other scripts can be written on the flash.
Anyway, thanks for explaining,
Stav
-
bitstopjoe
- Future magicJack CEO
- Posts: 2844
- Joined: Sat Sep 13, 2008 5:25 pm
- Location: North East Pennsylvania
running mj as service no longer works
after an update last night to 1.80.499.2, when i run mj as a service the quality is very bad. any clues is if this is still possible with the new update?
-
bitstopjoe
- Future magicJack CEO
- Posts: 2844
- Joined: Sat Sep 13, 2008 5:25 pm
- Location: North East Pennsylvania
I never ran mine as a service so I cant say for sure. Maybe undo it running as a service and see how it works then. OR go to their web page and d/l the update and run it again..
Since it has been about 2 weeks since the update I am sure we would have heard on this forum if running it as a service no longer worked...
Joe Sica
Since it has been about 2 weeks since the update I am sure we would have heard on this forum if running it as a service no longer worked...
Joe Sica
Last edited by bitstopjoe on Wed Aug 12, 2009 7:16 pm, edited 1 time in total.
magic jack as service
i revisited the link:
http://www.phoneservicesupport.com/magi ... t1364.html
i changed the parameters for the executable in the registry to the localservice directory in C:\Documents and Settings\LocalService. i also changed the target as mentioned in the link to:
"C:\Documents and Settings\LocalService\Application Data\mjusbsp\magicJack.exe" /scf _magicJackPersonalDataRoot "J:\magicJack"
so far so good.
http://www.phoneservicesupport.com/magi ... t1364.html
i changed the parameters for the executable in the registry to the localservice directory in C:\Documents and Settings\LocalService. i also changed the target as mentioned in the link to:
"C:\Documents and Settings\LocalService\Application Data\mjusbsp\magicJack.exe" /scf _magicJackPersonalDataRoot "J:\magicJack"
so far so good.