magicJack and magicJack Plus Support, Reviews, FAQs and Tricks

krzysiek841 wrote:i changed the cpu later
still the same
its bios or windows problem ...
but why in mini winxp launched from cd, cpu-z shows normally 4GB
and the system see only 3,5

XP always showed 3.5GB when working with 4GB
It was a system limitation of the OS and its 32-bit system.

I'm curious why HP seems to have limited the BIOS when in a 64-bit OS
to not use the full 4GB of RAM and go to blue-screen

The chipset DataSheet of the T5730/35 says it supports 8GB of RAM.
I guess now, it may be the BIOS limitation, as the other polish site said

Have you put the other resistor R473 (4.7k ohm) and capacitor needed?

yes the are all there
but a asked earkier about:

maybe C243 ? is atached on the images from gt thin client
but t5730 is not present
http://imgur.com/a/OBP2c

maybe that could be the problem

do you know an other windows based system that could work with 4GB
xp 64 ? - i know that it is not good full of errors

krzysiek841 wrote:yes the are all there
but a asked earkier about:

maybe C243 ? is atached on the images from gt thin client
but t5730 is not present
http://imgur.com/a/OBP2c

maybe that could be the problem

I don't think the C243 would do it.
If a resistor was missing, it would not power a section of the socket,
But the capacitor missing would just allow RF noise in and make artifacts
on the screen.

This seems like the BIOS limit, but...
.. I'm still checking stuff with that other capacitor
C243... If any importance, it may just be a power filtering capacitor, to smooth voltage.
That capacitor looks bigger on the board trace, than the other capacitor.

R470 and R239 would seem more important there.

Do those show on the T5730 board?

krzysiek841 wrote:
do you know an other windows based system that could work with 4GB
xp 64 ? - i know that it is not good full of errors

You added this after I replied

Do you have Linux 64-bit?

XP 64 is very old and not updated in 10 years.

You said you tried Win7 - 64-bit
But do you have Windows 8.1 pro 64-bit?

i dont want linux
but 8.1 could be the thing
i would install i tomorrow and will se
i will wright then if it works ...

krzysiek841 wrote:i dont want linux
but 8.1 could be the thing
i would install i tomorrow and will se
i will wright then if it works ...

Yes, try to get the full Pro version of 8.1 to test with.
It has all the drivers needed, and full functions needed.

krzysiek841
I had another thought about this.
Maybe the both RAM modules need to be matched. The same types.
Speed and number of chips on each side too.

I'm guessing but if there are 8 resister packs, for each socket, maybe the T5730 is expecting modules with 8 chips on each side of the module for each socket.

Do you have modules of the same types.

Are the both 2GB modules you're using the same speed, same # of chips, same manufacturer?

i have two same kingston modules 800MHz
with 8 chips pro module side (16 chips pro module)

i have installed windows 8.1 64bit with 3GB RAM
after install i gave there 4GB and the tk restarts about 10 seconds after starting loading windows
also the same like windows 7 64bit
it looks like its bios ...
but what can we do with bios limits ... ?

found some sites with bios edit tools but dont know what to search in the bios...


https://sites.google.com/site/pinczakko ... pg-hacking

http://www.win-raid.com/t8f16-BIOS-Modd ... tions.html

https://www.bios-mods.com/downloads/

I have tried several distros of linux and none of them had the appropriate video driver to allow you to see the GUI on these little thin clients. The only one I have found to work is puppy linux. You might try using this link and make a bootable copy of puppy linux and see if you can get it to work with 4gb of ram with it. That would just be one more tool to make sure it is the bios.
http://puppylinux.org/wikka/BootFlash

krzysiek841 wrote:found some sites with bios edit tools but dont know what to search in the bios...


https://sites.google.com/site/pinczakko ... pg-hacking

http://www.win-raid.com/t8f16-BIOS-Modd ... tions.html

https://www.bios-mods.com/downloads/

Hi guys,
This is very distressful.
All that work, krzysiek841, and still no happiness

It seems this link...
http://www.win-raid.com/t8f16-BIOS-Modd ... tions.html
...may be the best option for our situation.

krzysiek841 may be best to speak to the author of that thread, as he's in Germany too, and easier to speak with, do to no language barriers.

I'm hoping, if it's possible, to take the RAM controller section of the T5730 and modify it with the similar parameters of the GT7725 or T5740 that use two RAM sockets. If comparing it makes it easier to see what's different in the T5730, from the other two.

This other links thread author may be able to show us, or krzysiek841 how to do it, or may do it himself, for a fellow countryman.

I have no idea how to do this, and wouldn't even no where to start.
But be careful, if you flash the bios and it turns out totally wrong, your working T5730 is gone.

An idea, if your other T5730/35 is still bootable, but just the RAM socket was messed-up, you could use that to see if the mod'd bios lets the unit still boot, without sacrificing your working unit with the good socket.

T5735 wrote:I have tried several distros of linux and none of them had the appropriate video driver to allow you to see the GUI on these little thin clients. The only one I have found to work is puppy linux. You might try using this link and make a bootable copy of puppy linux and see if you can get it to work with 4gb of ram with it. That would just be one more tool to make sure it is the bios.
http://puppylinux.org/wikka/BootFlash

Yeah...this is a VERY good idea to at least determine if it's the OS limitations, or the BIOS

But it seems a 64-bit OS is having troubles with the extra RAM.
is this 64-bit?

It doesn't seem to mention it on that linked page.

I just realized something, and a good reason why I can't be the one to modify our BIOS file.

That other link I said was our best choice for our modification, seems to just be dealing with hard drive sections in the bios file.

Unless this person may also know other sections, and how to modify it as well.

Maybe krzysiek841 can ask him, just to be sure.

EDITED... Sept.23rd ,2014
He asked, and they said they're not a SYSTEM BIOS modding site, just for RAID Modules in it.

Well I took the heat sink off of my ATI HDMI graphics card today and installed it in the expansion module for the GT7725 and it works just fine. It booted up and found the drivers from the internet and installed fine. I got both HD video and audio out with it to my tv so now I just need to look around for a graphics card that meets my needs on ebay and I should be set.

i have asked about it ...
t5735 do you have tried 2x2GB in your GT TK ?

No I actually put the last pair of them I had in my aunts laptop that she brought to me because it was slow. I still have my single 2gb stick in my T5735 that I can remove and put in with a single stick into the GT7725 to see if 3gb works at least. I have been watching ebay to see if I can't snag another stick or two for cheap. I do run two DDR3 2gb sticks in my T5740 and it runs just fine though.

hi
i am confused
puppy 5.7.0






also 4GB works or not ?

when it works then why windows based x64 systems didn't work ...

I used that BIOS reading tool from that bios modding site,
to 'look into' the T5730 BIOS file, and got this info...

http://i.imgur.com/35y576x.jpg

Maybe you can post it to that guy to ask what may be needed to be modified,
In other words, what section in that list deals with the RAM controller,
if he may know.

krzysiek841 wrote:hi
i am confused
puppy 5.7.0


http://i58.tinypic.com/53jxqb.jpg
http://i60.tinypic.com/21kjpxg.jpg


also 4GB works or not ?

when it works then why windows based x64 systems didn't work ...

I suspect the 64-bit OS may be having problems putting the RAM in Dual-Channel mode

Well at least we know it isn't the bios now right? If puppy linux can see and use all of it.

T5735 wrote:Well at least we know it isn't the bios now right? If puppy linux can see and use all of it.

That still doesn't make sense though.
The OS isn't totally separate from the hardware.
Even though many parts of these mods 'defied' what seemingly the BIOS didn't allow, it was still over-ruled by the OS.

Example--- the CPU shows differently named in the BIOS, but the OS accepts it, and correctly shows the dual-core CPU being used.

If this IS the case, then it's still a hardware issue
(maybe missing resistor...etc) that's otherwise unknown.

Maybe even a jumper somewhere not normally seen on the TC's using two RAM sockets.

Something that's not setting the OS into dual-channel RAM socket mode.

I posted a question to that RAID BIOS modding site...
http://www.win-raid.com/t8f16-BIOS-Modd ... ml#msg8519
...with the screen-capture photo of the BIOS sections.

Maybe he can suggest the section of the BIOS to view and compare on our ThinClient between the T5740/45 or GT7725 and the T5730/35

momo wrote:

T5735 wrote:Well at least we know it isn't the bios now right? If puppy linux can see and use all of it.

That still doesn't make sense though.
The OS isn't totally separate from the hardware.
Even though many parts of these mods 'defied' what seemingly the BIOS didn't allow, it was still over-ruled by the OS.

Example--- the CPU shows differently named in the BIOS, but the OS accepts it, and correctly shows the dual-core CPU being used.

If this IS the case, then it's still a hardware issue
(maybe missing resistor...etc) that's otherwise unknown.

Maybe even a jumper somewhere not normally seen on the TC's using two RAM sockets.

Something that's not setting the OS into dual-channel RAM socket mode.

It has been my experience that the pc will still use the ram not in dual channel if it tries and finds two different sticks. I wonder if you mixed two different brand 2gb sticks if that would make any difference?

T5735 wrote:

momo wrote:

T5735 wrote:Well at least we know it isn't the bios now right? If puppy linux can see and use all of it.

That still doesn't make sense though.
The OS isn't totally separate from the hardware.
Even though many parts of these mods 'defied' what seemingly the BIOS didn't allow, it was still over-ruled by the OS.

Example--- the CPU shows differently named in the BIOS, but the OS accepts it, and correctly shows the dual-core CPU being used.

If this IS the case, then it's still a hardware issue
(maybe missing resistor...etc) that's otherwise unknown.

Maybe even a jumper somewhere not normally seen on the TC's using two RAM sockets.

Something that's not setting the OS into dual-channel RAM socket mode.

It has been my experience that the pc will still use the ram not in dual channel if it tries and finds two different sticks. I wonder if you mixed two different brand 2gb sticks if that would make any difference?

According to another link I posted, earlier in this thread,
it mentioned to someone else, asking about needing matched pair modules...
it said basically, if they are not matched depending on the systems BIOS,
it may work, but not use them as dual-channel, or not even boot the system.

I asked krzysiek841 if he tried same type sticks, he said yes (the 2 x 2GB)
I don't know if he tried different types using his 2GB and 1GB combination for 3GB total.

If the 3GB combo of differing sticks works,
does that indicate it may be a dual-channel issue, with similar 2x 2GB sticks?

3GB works no problem, 1,5 GB no problem too (2+1)(1+0,5)
my 2x2GB are identical but i dont have any other 2GB to try

krzysiek841 wrote:3GB works no problem, 1,5 GB no problem too (2+1)(1+0,5)
my 2x2GB are identical but i dont have any other 2GB to try

Does the 3GB combo also work on the 64-bit OS or just the 32-bit?

3GB works on 64 and 32 bit system

krzysiek841 wrote:3GB works on 64 and 32 bit system

Thanks, I didn't know that.

Interesting that the extra 1GB in the 2nd socket (2GB) would give blue-screen and reboot in 64-bit OS
It still doesn't confirm (for me) if it's hardware limits, or BIOS limits.

If 3GB works with a 64-bit OS it may actually be the BIOS limiting it with 2x2GB sticks

That's strange though.

I checked krzysiek841's statement on that RAID BIOS modding site,
and he said the 2GB module works separately in each socket, alone,
but when used together they don't.

So, I'm thinking if there was a hardware problem with the 2nd socket,
it wouldn't have even worked separately in the 2nd socket.

Does my logic sound correct?

Is there anything else I'm not considering, hardware wise?


I'm still wondering why HP would have limited the total RAM allowed,
when everything else in the BIOS allows all other mods to be used.

momo wrote:I checked krzysiek841's statement on that RAID BIOS modding site,
and he said the 2GB module works separately in each socket, alone,
but when used together they don't.

So, I'm thinking if there was a hardware problem with the 2nd socket,
it wouldn't have even worked separately in the 2nd socket.

Does my logic sound correct?

Is there anything else I'm not considering, hardware wise?

The only other part, is if the GT7725 and T5740/45 works with both 2GB modules
in each socket, at the same time (together).

I'm still wondering why HP would have limited the total RAM allowed,
when everything else in the BIOS allows all other mods to be used.

But it's a good chance the only thing left is the BIOS.

The T5740 works with two DDR3 2gb sticks in it. I have several operating that way.

T5735 wrote:

momo wrote:I checked krzysiek841's statement on that RAID BIOS modding site,
and he said the 2GB module works separately in each socket, alone,
but when used together they don't.

So, I'm thinking if there was a hardware problem with the 2nd socket,
it wouldn't have even worked separately in the 2nd socket.

Does my logic sound correct?

Is there anything else I'm not considering, hardware wise?

The only other part, is if the GT7725 and T5740/45 works with both 2GB modules
in each socket, at the same time (together).

I'm still wondering why HP would have limited the total RAM allowed,
when everything else in the BIOS allows all other mods to be used.

But it's a good chance the only thing left is the BIOS.

The T5740 works with two DDR3 2gb sticks in it. I have several operating that way.

OK, then if no other unknown hardware difference exists, between the T5730/35 and the T5740/45
it must be the BIOS difference on each.

I also tried to find the BIOS ROM chip, and may have located it, on the T5730
but my chip is hard to read. The writing is faded.

Can you check your T5730 and try to get a very close very well focused photo
of the chip to the left of the CMOS battery?

It's a 8-pin SMD chip.
This is either the BIOS ROM, or simply the CMOS chip, but I can't see the printing
to get its part number.

momo wrote:

T5735 wrote:

momo wrote:I checked krzysiek841's statement on that RAID BIOS modding site,
and he said the 2GB module works separately in each socket, alone,
but when used together they don't.

So, I'm thinking if there was a hardware problem with the 2nd socket,
it wouldn't have even worked separately in the 2nd socket.

Does my logic sound correct?

Is there anything else I'm not considering, hardware wise?

The only other part, is if the GT7725 and T5740/45 works with both 2GB modules
in each socket, at the same time (together).

I'm still wondering why HP would have limited the total RAM allowed,
when everything else in the BIOS allows all other mods to be used.

But it's a good chance the only thing left is the BIOS.

The T5740 works with two DDR3 2gb sticks in it. I have several operating that way.

OK, then if no other unknown hardware difference exists, between the T5730/35 and the T5740/45
it must be the BIOS difference on each.

I also tried to find the BIOS ROM chip, and may have located it, on the T5730
but my chip is hard to read. The writing is faded.

Can you check your T5730 and try to get a very close very well focused photo
of the chip to the left of the CMOS battery?

It's a 8-pin SMD chip.
This is either the BIOS ROM, or simply the CMOS chip, but I can't see the printing
to get its part number.

The T5740 is a totally different thin client that runs on a Atom CPU and uses DDR3 ram and has onboard SATA connections.

T5735 wrote: The T5740 is a totally different thin client that runs on a Atom CPU and uses DDR3 ram and has onboard SATA connections.

Hmmm, well, but the T5730/35 chipset's DataSheet says it supports up to 8GB of RAM.

So, something is limiting it. Even if the two systems hardware is completely different.

I may have nothing to compare BIOS's with, if the two are that much different

As hard as I tried I could not get a good clear image of that chip. It is really rainy and overcast here so if it is nicer tomorrow I will try to take it outside in the sunlight and get a good clear picture.
http://imgur.com/e92Akfy

I think I may need to clarify what I meant by 'no hardware differences'

Mostly, I'm referring to the resisters and capacitors around the RAM sockets.

That's basically similar .. I hope.

By the way, that 4.7k ohm SMD resistor measured for the use in the T5730
was read from the GT7725. So unless the T5730/35 has a different value,
because of the different DDR3 in the GT7725, instead of the DDR2 T5730
may also play a part in this, but that may not make a difference.

Besides krzysiek841 used resistors and capacitors from his damaged 2nd T5730/35

If you have a T5730 that's got the mobo out,
you can see if the resistor that matches it's placement measures the same.

The GT7725 uses the DDR2 ram just like the T5730/35 does. I will see about taking the motherboard out tomorrow and seeing what I can do about testing the resistors on a T5735.

T5735 wrote:As hard as I tried I could not get a good clear image of that chip. It is really rainy and overcast here so if it is nicer tomorrow I will try to take it outside in the sunlight and get a good clear picture.
http://imgur.com/e92Akfy

Wow, yours looks like it's in a socket. .. Mine isn't
I'll need to transfer my pix from the Canon camera thru USB on my computer
to show you what I was able to see.

Is this (your photo) the T5735/30 ... or the T5740 ?

momo wrote:

T5735 wrote:As hard as I tried I could not get a good clear image of that chip. It is really rainy and overcast here so if it is nicer tomorrow I will try to take it outside in the sunlight and get a good clear picture.
http://imgur.com/e92Akfy

Wow, yours looks like it's in a socket. .. Mine isn't
I'll need to transfer my pix from the Canon camera thru USB on my computer
to show you what I was able to see.

Is this (your photo) the T5735/30 ... or the T5740 ?

It is a picture of a T5735 motherboard. The T5735 is just the linux version of the T5730.

T5735 wrote:

momo wrote:

T5735 wrote:As hard as I tried I could not get a good clear image of that chip. It is really rainy and overcast here so if it is nicer tomorrow I will try to take it outside in the sunlight and get a good clear picture.
http://imgur.com/e92Akfy

Wow, yours looks like it's in a socket. .. Mine isn't
I'll need to transfer my pix from the Canon camera thru USB on my computer
to show you what I was able to see.

Is this (your photo) the T5735/30 ... or the T5740 ?

It is a picture of a T5735 motherboard. The T5735 is just the linux version of the T5730.

Interesting...my T5730 has those other two IC's in a different position.
Maybe the T5735 has slightly different parts placements from the T5730

momo wrote:

T5735 wrote:

momo wrote: Wow, yours looks like it's in a socket. .. Mine isn't
I'll need to transfer my pix from the Canon camera thru USB on my computer
to show you what I was able to see.

Is this (your photo) the T5735/30 ... or the T5740 ?

It is a picture of a T5735 motherboard. The T5735 is just the linux version of the T5730.

Interesting...my T5730 has those other two IC's in a different position.
Maybe the T5735 has slightly different parts placements from the T5730

Yours also did not come with a mini pci-e slot on the back of the motherboard so could that have anything to do with it? This picture from the parkytowers site looks like my motherboard.
http://www.parkytowers.me.uk/thin/hp/t5 ... inside.jpg
and this one from a google image search looks the same as mine as well.
http://i00.i.aliimg.com/wsphoto/v0/8586 ... rd-AMD.jpg
Also here is a ebay auction for a bios chip.
http://www.ebay.com/itm/BIOS-CHIP-hp-Co ... 0659924855

T5735 wrote:

momo wrote:

T5735 wrote: It is a picture of a T5735 motherboard. The T5735 is just the linux version of the T5730.

Interesting...my T5730 has those other two IC's in a different position.
Maybe the T5735 has slightly different parts placements from the T5730

Yours also did not come with a mini pci-e slot on the back of the motherboard so could that have anything to do with it? This picture from the parkytowers site looks like my motherboard.
http://www.parkytowers.me.uk/thin/hp/t5 ... inside.jpg
and this one from a google image search looks the same as mine as well.
http://i00.i.aliimg.com/wsphoto/v0/8586 ... rd-AMD.jpg

Possibly.
I wonder if there are any differences with the BIOS, but I think you use the exact same BIOS file as I do, right?
Maybe they just needed to move stuff around to accommodate for the mini pice socket,
or simply just upgraded the design for other reasons

I'm transferring that photo to my computer now then I'll send it to my iPad to upload to the photo site.

OK, false alarm..
The IC placement is the same on both (mine and yours)

I got disoriented with the flipped photo for awhile.

But now that I see yours is socketed, it's more likely that's the BIOS chip on mine and yours.

momo wrote:
OK, false alarm..
The IC placement is the same on both (mine and yours)

I got disoriented with the flipped photo for awhile.

But now that I see yours is socketed, it's more likely that's the BIOS chip on mine and yours.

I think there is no doubt that it is the bios chip after looking at this ebay auction.
http://www.ebay.com/itm/BIOS-CHIP-hp-Co ... 0659924855

T5735 wrote:

momo wrote:
OK, false alarm..
The IC placement is the same on both (mine and yours)

I got disoriented with the flipped photo for awhile.

But now that I see yours is socketed, it's more likely that's the BIOS chip on mine and yours.

I think their is no doubt that it is the bios chip after looking at this ebay auction.
http://www.ebay.com/itm/BIOS-CHIP-hp-Co ... 0659924855

Yeah, but I still want to know the part number, because I may be able to re-program it,
if we play with the bios in any way, so I don't brick your system or krzysiek841's

I can test the modded bios on mine until it can boot up without problems.

This is a zoomed image of the original, from a screen capture on my iPad
http://i.imgur.com/AuoTFfj.jpg

This is the original from my Canon 8.5 Mpixel camera
http://i.imgur.com/AVQQTmZ.jpg

I think that photo site re-sizes the photos, because my true original is over 3000 x 2000 pixels

EDITED...
Photo info shown with my transfer app on my iPad
http://i.imgur.com/1guEW2V.jpg

i have unsoldered the capacitor from my broken T5730 (from the 1 socket) but the 4k7 resistors comes from an other place from the motherboard from the broken tc ... so i think its posible that the value is false ...

my bios is in a socket too (in currently working tc) but in the broken one its soldered to motherboard and the broken mobo hasn't got the mini pcie socket

the bios chip for you momo 25l4005am2c

krzysiek841 wrote:i have unsoldered the capacitor from my broken T5730 (from the 1 socket) but the 4k7 resistors comes from an other place from the motherboard from the broken tc ... so i think its posible that the value is false ...

Did you measure the resistor value before soldering it?
If the 2nd socket is working, separately with a 2GB module, it's most likely OK

my bios is in a socket too (in currently working tc) but in the broken one its soldered to motherboard and the broken mobo hasn't got the mini pcie socket

Yeah, T5735 said the socketed bios chip boards also have the mini-PCIe connector on the back.

the bios chip for you momo 25l4005am2c

Data sheet for the bios chip
http://www.ic-on-line.cn/download.php?i ... 351093.pdf

Thanks for looking
I need to check if my programmer supports this, but I think it will.
I may not even need to remove it, and may be able to read and program it while it's in-circuit.
But even if not, I can remove it too, with my SMD rework tool.