MJ Ready Thin Clients on Sale Now From Just $55 Shipped!!
Moderators: Bill Smith, Pilot
TC3350
Alpman:
I just wanted to thank you again! After spending days reading through post about obtaining my SIP credentials and attempting to get my PAP2 to work with MJ, I stumbled upon your post for your thin clients. This was the best $55 I've spent in a while. I don't know anyone who has a quicker turn around than you. I ordered the TC on Wednesday and had it delivered on Friday!!! That's from CA to SC in 2 days!!! I had a few questions and you answered them quickly.
Plug the device in. Wait about 5 min or so and you're off. Thank you.
I just wanted to thank you again! After spending days reading through post about obtaining my SIP credentials and attempting to get my PAP2 to work with MJ, I stumbled upon your post for your thin clients. This was the best $55 I've spent in a while. I don't know anyone who has a quicker turn around than you. I ordered the TC on Wednesday and had it delivered on Friday!!! That's from CA to SC in 2 days!!! I had a few questions and you answered them quickly.
Plug the device in. Wait about 5 min or so and you're off. Thank you.
-
Alpman
- Dan isn't smart enough to hire me
- Posts: 260
- Joined: Wed Sep 03, 2008 6:14 am
- Location: Sierra Nevada Foothills - Frogtown, Ca
- Contact:
Check my first post on the first page and you will find pricing/availability of models. I do not have any currently listed on eBay but I am accepting PayPal payments to the email in my signature. ust select the model you wish to purchase, send payment and I'll build, test and ship it usually the same day as payment. Thanks for your interest. If you have further questions you can PM or email me.
-
Paul777
- Dan isn't smart enough to hire me
- Posts: 168
- Joined: Tue Apr 20, 2010 10:46 pm
- Location: Toronto, ON
Ship to Canada
Yes I think he ships to Canada. Alpman I'm willing to buy two units from you. I've tried looking around here for some cheap TC's. No one comes close to your price ! Unless there are serious issues with them.
I bought 4 units for $100 through a guy on Kijiji. Out of the 4 only 1 works with MJ. The other literally hangs when receiving a call, and the other 2 are linux and one of those doesn't boot. I guess I did okay but too much time spent trying to see what the issues were and trying to find a fix. TC's are new concept for me, but just don't know enough about adding memory, flashing for upgrades to OS.
Anyway when you get back online, I'd sure like a quote for two units. I know other people with MJ's and I need one for faxing on another MJ.
If it would be significantly cheaper, as an alternate could you ship to Michigan? I do visit a buddy there from time to time and I could pick them up there.
Thanks.
I bought 4 units for $100 through a guy on Kijiji. Out of the 4 only 1 works with MJ. The other literally hangs when receiving a call, and the other 2 are linux and one of those doesn't boot. I guess I did okay but too much time spent trying to see what the issues were and trying to find a fix. TC's are new concept for me, but just don't know enough about adding memory, flashing for upgrades to OS.
Anyway when you get back online, I'd sure like a quote for two units. I know other people with MJ's and I need one for faxing on another MJ.
If it would be significantly cheaper, as an alternate could you ship to Michigan? I do visit a buddy there from time to time and I could pick them up there.
Thanks.
Paul777 in Canada
-
conniemadagain
- Dan isn't smart enough to hire me
- Posts: 396
- Joined: Tue Mar 31, 2009 11:57 am
-
kos99ngel
- magicJack Apprentice
- Posts: 28
- Joined: Mon Mar 29, 2010 6:43 pm
- Location: Los Angeles 213 Pico Union District
This is a "Thin" Computer with enough power to run Windows XP, the MagicJack software. There is no hard disk drive, fans or any moving parts. It is called a solid state device. It also uses very little power (Less than 8 watts). Most people buy something like this to so their MagicJack system is not dependent on their main computer constantly running and connected to the internet. You can think of this as a "Phone System" computer specially configured for MagicJack.Alphamale wrote:What are these devices?
-
conniemadagain
- Dan isn't smart enough to hire me
- Posts: 396
- Joined: Tue Mar 31, 2009 11:57 am
YUP ... I still have mine from alpman w/upgraded memory ...
guess i should sell it ...
guess i should sell it ...
kos99ngel wrote:This is a "Thin" Computer with enough power to run Windows XP, the MagicJack software. There is no hard disk drive, fans or any moving parts. It is called a solid state device. It also uses very little power (Less than 8 watts). Most people buy something like this to so their MagicJack system is not dependent on their main computer constantly running and connected to the internet. You can think of this as a "Phone System" computer specially configured for MagicJack.Alphamale wrote:What are these devices?
Damit Jim, I'm just a GOD!
It's not a big deal to get MJ to run on a thin client, assuming the unit is already flashed with a working XPe OS. You don't need someone else to configure or set it up for you. It takes about 5 minutes to configure the BIOS and OS, using the guidance available on this site. I've only used the Wyse units, but as long as it has enough RAM (512 for the Wyse), and enough flash (also 512 for the Wyse), and has the VIA C7 processor, at any speed), it is a snap to install and run the current MJ device, so long as the TC is dedicated to that purpose. Even the 1000MHz C3 processors (Wyse V90, 941GXL) worked OK, but the ones slower than that were about borderline, at least in my hands. The C7 XPe units (V90L/LE series, C90L/LE/LEW/LE7 series TCs) are also easily re-flashed with a USB thumb drive, and freeware from the Wyse site.
Since the V90 units can be regularly had on eBay for $40-$60 (and were typically built with 512/512 or greater, unlike the older units) I don't see why anyone would opt for the older TCs, whether pre-configured for MJ or not.
By the way, these units run at about 14-18W for the V90s, 7W for the C90s. The C90s go to 0 watts if you shut down the TC but leave it plugged in, the others still burn about 4W.
Since the V90 units can be regularly had on eBay for $40-$60 (and were typically built with 512/512 or greater, unlike the older units) I don't see why anyone would opt for the older TCs, whether pre-configured for MJ or not.
By the way, these units run at about 14-18W for the V90s, 7W for the C90s. The C90s go to 0 watts if you shut down the TC but leave it plugged in, the others still burn about 4W.
Need your help if possible:spoolin01 wrote:It's not a big deal to get MJ to run on a thin client, assuming the unit is already flashed with a working XPe OS. You don't need someone else to configure or set it up for you. It takes about 5 minutes to configure the BIOS and OS, using the guidance available on this site. I've only used the Wyse units, but as long as it has enough RAM (512 for the Wyse), and enough flash (also 512 for the Wyse), and has the VIA C7 processor, at any speed), it is a snap to install and run the current MJ device, so long as the TC is dedicated to that purpose. Even the 1000MHz C3 processors (Wyse V90, 941GXL) worked OK, but the ones slower than that were about borderline, at least in my hands. The C7 XPe units (V90L/LE series, C90L/LE/LEW/LE7 series TCs) are also easily re-flashed with a USB thumb drive, and freeware from the Wyse site.
Since the V90 units can be regularly had on eBay for $40-$60 (and were typically built with 512/512 or greater, unlike the older units) I don't see why anyone would opt for the older TCs, whether pre-configured for MJ or not.
By the way, these units run at about 14-18W for the V90s, 7W for the C90s. The C90s go to 0 watts if you shut down the TC but leave it plugged in, the others still burn about 4W.
Which image would I need to download from Wyse for a VIA Ezra (C3) 800MHz processor (Maxterm 8300 TC)?
My MJ runs well on a Neoware CA10 which has the VIA C3 Nehemiah 800MHz processor and 512Mb Flash (DOM) and 512Mb RAM. The only difference between the Maxspeed 8300 and the CA10 is that the Maxspeed has a CF instead of a DOM.
Any help would be appreciated.
I don't know if I'm smart enough to help you out - I should say I'm not a techie and what little I know of PCs I've just picked up by playing around. I've stuck to running Wyse images on Wyse boxes, and also some retail XP stripped down via nLite.murugan wrote: Need your help if possible:
Which image would I need to download from Wyse for a VIA Ezra (C3) 800MHz processor (Maxterm 8300 TC)?
My MJ runs well on a Neoware CA10 which has the VIA C3 Nehemiah 800MHz processor and 512Mb Flash (DOM) and 512Mb RAM. The only difference between the Maxspeed 8300 and the CA10 is that the Maxspeed has a CF instead of a DOM.
Any help would be appreciated.
I don't know of any Wyse boxes that used the Ezra, but the 9450/9455 used the VIA C3 Samuel, which I just read on Wikipedia was the close precursor to Ezra. The latest images for those (I think they shared images) are on the Wyse site, and they were 512 flash machines. They come packaged for Wyse management software, so you'll have to know how to get what you want out of their image. I don't know how the rest of the mobo matches up between those and yours - the VIA site might help with any drivers you might need for your board (I'm assuming it's a VIA board).
I don't know how closely matched the drivers need to be for the image to work passably, or if there are other considerations in build compatibility, but the 941GXL, and the V90 (not the V90L or LE) also used a later C3 CPU and XPe, and there were images for those for use with 512MB flash. I don't know what other changes there were in the mobo components, but that info is out there, I'm sure.
If the 9450/9455 images don't work for you, I wonder if it wouldn't be easier to start with full XP and strip it down via nLite or similar, so you have access to the various hardware-dependent libraries during installation. Then the VIA site should be able to get you the exact drivers you need for your mobo.
If you don't have the ability to image your device with one of the Wyse images directly, a workaround would be to have someone with a 9450 or 9455 take your flash, and image it in their box.
You may already know all of this, and some of it may be off the mark, but I've tried to download what I *think* I know about this.
This also gets into licensing issues perhaps, that I can't advise on. I'm not familiar with the restrictions attached to XPe and/or Wyse image licensing, but I'll bet they're tight.
Maxterm 8300 - similar to Wyse 9450/9455/V90/941GXL?
Hi spoolin01,
Thank you for the quick reply.
I'll try imaging the CF with the above images. XPE is actually built on the machine it is intended to run so it's production image is identical to the hardware it was built for. Unlike the std XP, it does not install any drivers when it finds them, as it was targeted for specific hardware (ie: graphics, USB, LAN, etc)
For that reason, if the Maxterm 8300 differed from any of the models listed by you, their respective images will not boot (unable to find drivers for devices in the Maxterm 8300 rather than the Wyse). But it does not hurt me to try as Wyse may have used the same VIA mobo and chipset as Maxspeed.
"If you don't have the ability to image your device with one of the Wyse images directly, a workaround would be to have someone with a 9450 or 9455 take your flash, and image it in their box."
If the 9450/9455 images work, then I don't need anyone to image my CF in their box - my CF can be imaged in my box with a dd command.
Using a full XP and nLite to strip it down doesn't work either for reasons in the first/second paragraphs above and most importantly, XPE does not write to the CF or DOM or any flash memory - they can only stand so many writes before they are wear leveled out. XPE installs a EWF (Enhanced Write Filter) or a FBWF (File based write filter) to make sure that nothing is written to the flash. This was also a security feature that made TCs attractive - end user mods couldn't be done without Admin or root rights.
I'll try the above images and let you know if they work. Thanks for the suggestions. I won't get into any licensing issues as I own the original CF with it's COA - all I'm trying to do is set it right as Maxspeed Maxterm is now a defunct company and this is my only recourse.
Thank you for the quick reply.
I'll try imaging the CF with the above images. XPE is actually built on the machine it is intended to run so it's production image is identical to the hardware it was built for. Unlike the std XP, it does not install any drivers when it finds them, as it was targeted for specific hardware (ie: graphics, USB, LAN, etc)
For that reason, if the Maxterm 8300 differed from any of the models listed by you, their respective images will not boot (unable to find drivers for devices in the Maxterm 8300 rather than the Wyse). But it does not hurt me to try as Wyse may have used the same VIA mobo and chipset as Maxspeed.
"If you don't have the ability to image your device with one of the Wyse images directly, a workaround would be to have someone with a 9450 or 9455 take your flash, and image it in their box."
If the 9450/9455 images work, then I don't need anyone to image my CF in their box - my CF can be imaged in my box with a dd command.
Using a full XP and nLite to strip it down doesn't work either for reasons in the first/second paragraphs above and most importantly, XPE does not write to the CF or DOM or any flash memory - they can only stand so many writes before they are wear leveled out. XPE installs a EWF (Enhanced Write Filter) or a FBWF (File based write filter) to make sure that nothing is written to the flash. This was also a security feature that made TCs attractive - end user mods couldn't be done without Admin or root rights.
I'll try the above images and let you know if they work. Thanks for the suggestions. I won't get into any licensing issues as I own the original CF with it's COA - all I'm trying to do is set it right as Maxspeed Maxterm is now a defunct company and this is my only recourse.
I don't recall the mobo model in the 9450/9455 but I have a couple here and I can check if you want to take a look at yours, before diving into the Wyse image. I found quite a bit of information about the board when I looked into it. It's the first EPIA mobo, I think, I just don't recall the number.
I forgot about the write filter, though I have made small XP installs with nLite that run on those older Wyse units - around 250MB as I recall. I think I just ran them from a HD. The VIA CPU and chipset drivers can be had from VIA if they're not already in the XP install package. I've read about adding write filters after the fact, but never tried it. At any rate, if you can work with the Wyse image as is, all the better. That starts to get beyond my ken.
I forgot about the write filter, though I have made small XP installs with nLite that run on those older Wyse units - around 250MB as I recall. I think I just ran them from a HD. The VIA CPU and chipset drivers can be had from VIA if they're not already in the XP install package. I've read about adding write filters after the fact, but never tried it. At any rate, if you can work with the Wyse image as is, all the better. That starts to get beyond my ken.
Wyse 9450/9455 = to Maxterm 8300?
Thanks spoolin01 for the fast response.
From replies I received, it appears that the Maxterm 8300 is a VIA 800 MHz Ezra with a VT133 chipset and a standard mini-itx mobo with a standard PC Award BIOS (not specially built for Maxspeed Corp).
From my research on the web, the Wyse V90L and the Neoware CA2 seem to be the nearest matches to the hardware (see http://www.parkytowers.me.uk/thin/hware/hardware.shtml).
I'm not sure if the 9450/9455 is the same but would be grateful if you have any info that would help me confirm the CPU as Ezra and chipset as VT133.
Thanks again for your help.
From replies I received, it appears that the Maxterm 8300 is a VIA 800 MHz Ezra with a VT133 chipset and a standard mini-itx mobo with a standard PC Award BIOS (not specially built for Maxspeed Corp).
From my research on the web, the Wyse V90L and the Neoware CA2 seem to be the nearest matches to the hardware (see http://www.parkytowers.me.uk/thin/hware/hardware.shtml).
I'm not sure if the 9450/9455 is the same but would be grateful if you have any info that would help me confirm the CPU as Ezra and chipset as VT133.
Thanks again for your help.
My recollection was a little off. The VIA Apollo PL133 is the chipset on the C3 boards in the 9450/9455. I don't find much info on the VIA VT133 but it appears to be contemporary with the C3 board in those two Wyse units. They use PC133 SDRAM. The V90 had DDR RAM, and a newer chipset. There was a C3 Nehemiah board in the Wyse 941GXL that was also PC133. But again, the info I saw was that the Samuel (9450/55) and Ezra were closely related, the Nehemiah was a generational change. I'd say one of those two (9450/55 or 941GXL) would be your best bet.
I just re-read your last post and saw you mentioned actually the V90L. The "L" was the VIA C7 processor, quite a change from the Ezra.
I'm curious though, about the need to match so closely. Can't you just get the VIA drivers for their CPU and chipset (get a bunch of them if it's not clear exactly which to use), and stuff them into either the image, or onto the flash, during the imaging of your flash? I see a lot of hits returned on a search for VT133 drivers, including a comment in a forum that VIA recommends standard XP drivers for that chipset.
I just re-read your last post and saw you mentioned actually the V90L. The "L" was the VIA C7 processor, quite a change from the Ezra.
I'm curious though, about the need to match so closely. Can't you just get the VIA drivers for their CPU and chipset (get a bunch of them if it's not clear exactly which to use), and stuff them into either the image, or onto the flash, during the imaging of your flash? I see a lot of hits returned on a search for VT133 drivers, including a comment in a forum that VIA recommends standard XP drivers for that chipset.
Thanks spoolin01.
In reply to "I'm curious though, about the need to match so closely. Can't you just get the VIA drivers for their CPU and chipset (get a bunch of them if it's not clear exactly which to use), and stuff them into either the image, or onto the flash, during the imaging of your flash?"
The Wyse 94xx has the 500Mhz Samuel CPU whereas the VIA Ezra is a 800 Mhz CPU. Not only are the CPUs different but the mobo chipsets are too.
As I said, the XPe image is built for a specific platform because it has only the supporting software for the specific devices and that's why it is so small. With that said, I cannot use just any XPe image as it will not boot.
There is no "during the imaging of your flash" - the XPe OS for the TC is built on a production platform and targeted for the computer or TC or tablet etc that will run it. The image created on the production platform is then written to the flash (imaging process) which is nothing more than a linux dd command. (in simple terms: dd if=production image of=flash bs= count= etc)
In reply to "Actually, I just recalled your box boots from CF so you're not much constrained by flash size - why not install a 4GB CF card and just do a full XP install, or a smaller nLite version? I must be missing something."
Installing a nLite XP or full XP on a CF is not a very good idea as the CF card can only stand a certain number of writes before it eventually "wears" out (the paging file alone will destroy the CF as it constantly writes to the disk (CF)). XPe does not write to the flash (CF or DOM or DoC) as it uses a ramdrive.
That does not mean that applications cannot be added (depending on flash capacity) AND ramdrive capacity by disabling the EWF (or FBWF) and re-enabling (commit) after they are installed.
Unfortunately:
(a) the ramdrive size cannot be changed as it is set during the image build phase
(b) I would need a working XPe image (one that boots on my platform) before I can add ("stuff") additional drivers and applications which was why I posted in this forum for (Ref: My post Mon Jan 30, 2012 7:52 pm).
So why not install XPe on a working platform and build my own image from drivers etc from VIA? XPe is now EOL and most importantly, MS dictates it being used only by OEMs.
Hope that clears up your questions.
I may just go Linux (ThinClient or TS-O-Matic for the image) but it will not run MJ unless I install a VM or Wine which not only defeats the purpose of
Linux (it's like scratching your right ear with your left hand - could have used your right hand in the first place!), but MJ has serious performance hits in running in a VM like latency, etc. Pure Linux TC's can run MJ only through RDP which again defeats the purpose of having a standalone MJ headless unit.
I need to think about it or experiment with a bunch of prebuilt XPe images. Unfortunately, I cannot contact Maxspeed Corp as they are defunct, and I cannot contact RETEK (OEM who built my image for Maxspeed) as they are also defunct even though I have the COA etc of original XPe image.
In reply to "I'm curious though, about the need to match so closely. Can't you just get the VIA drivers for their CPU and chipset (get a bunch of them if it's not clear exactly which to use), and stuff them into either the image, or onto the flash, during the imaging of your flash?"
The Wyse 94xx has the 500Mhz Samuel CPU whereas the VIA Ezra is a 800 Mhz CPU. Not only are the CPUs different but the mobo chipsets are too.
As I said, the XPe image is built for a specific platform because it has only the supporting software for the specific devices and that's why it is so small. With that said, I cannot use just any XPe image as it will not boot.
There is no "during the imaging of your flash" - the XPe OS for the TC is built on a production platform and targeted for the computer or TC or tablet etc that will run it. The image created on the production platform is then written to the flash (imaging process) which is nothing more than a linux dd command. (in simple terms: dd if=production image of=flash bs= count= etc)
In reply to "Actually, I just recalled your box boots from CF so you're not much constrained by flash size - why not install a 4GB CF card and just do a full XP install, or a smaller nLite version? I must be missing something."
Installing a nLite XP or full XP on a CF is not a very good idea as the CF card can only stand a certain number of writes before it eventually "wears" out (the paging file alone will destroy the CF as it constantly writes to the disk (CF)). XPe does not write to the flash (CF or DOM or DoC) as it uses a ramdrive.
That does not mean that applications cannot be added (depending on flash capacity) AND ramdrive capacity by disabling the EWF (or FBWF) and re-enabling (commit) after they are installed.
Unfortunately:
(a) the ramdrive size cannot be changed as it is set during the image build phase
(b) I would need a working XPe image (one that boots on my platform) before I can add ("stuff") additional drivers and applications which was why I posted in this forum for (Ref: My post Mon Jan 30, 2012 7:52 pm).
So why not install XPe on a working platform and build my own image from drivers etc from VIA? XPe is now EOL and most importantly, MS dictates it being used only by OEMs.
Hope that clears up your questions.
I may just go Linux (ThinClient or TS-O-Matic for the image) but it will not run MJ unless I install a VM or Wine which not only defeats the purpose of
Linux (it's like scratching your right ear with your left hand - could have used your right hand in the first place!), but MJ has serious performance hits in running in a VM like latency, etc. Pure Linux TC's can run MJ only through RDP which again defeats the purpose of having a standalone MJ headless unit.
I need to think about it or experiment with a bunch of prebuilt XPe images. Unfortunately, I cannot contact Maxspeed Corp as they are defunct, and I cannot contact RETEK (OEM who built my image for Maxspeed) as they are also defunct even though I have the COA etc of original XPe image.
Does the CPU speed matter? Wyse underclocked their CPUs from what I can tell, probably for heat output. Wikipedia implied the Ezra is pretty much the same code as the Samuel, so if true, wouldn't the drivers be the same, or probably good enough for a first pass?murugan wrote:Thanks spoolin01.
In reply to "I'm curious though, about the need to match so closely. Can't you just get the VIA drivers for their CPU and chipset (get a bunch of them if it's not clear exactly which to use), and stuff them into either the image, or onto the flash, during the imaging of your flash?"
The Wyse 94xx has the 500Mhz Samuel CPU whereas the VIA Ezra is a 800 Mhz CPU. Not only are the CPUs different but the mobo chipsets are too.
Understood, but if you're going for the best shot, doesn't the Wyse Samuel image (9450) seem like the closest match? I haven't found any info on your mobo, can you tell what chips you've got? I just don't know much about this - how finely matched the drivers need to be or how thinly the builds shave the driver sets that VIA released, if at all.As I said, the XPe image is built for a specific platform because it has only the supporting software for the specific devices and that's why it is so small. With that said, I cannot use just any XPe image as it will not boot.
Once the image is loaded, while in the PXE environment, it's still under linux control. When you leave that, before it boots to Windows for the first time, can't you take the CF out and dump a VIA driver package into it? Doesn't that solve the problem of finding exactly the sole matching drivers? Just a speculation, but would that work?
There is no "during the imaging of your flash" - the XPe OS for the TC is built on a production platform and targeted for the computer or TC or tablet etc that will run it. The image created on the production platform is then written to the flash (imaging process) which is nothing more than a linux dd command. (in simple terms: dd if=production image of=flash bs= count= etc)
I was thinking in terms of lesser of two evils - if it's a matter of not being able to use the box at all. I've read various debates on how serious the risk of wearing out the flash is, and if the worst came to pass, a new CF isn't too spendy. Can the ramdrive and write filter be added on to a regular installation?In reply to "Actually, I just recalled your box boots from CF so you're not much constrained by flash size - why not install a 4GB CF card and just do a full XP install, or a smaller nLite version? I must be missing something."
Installing a nLite XP or full XP on a CF is not a very good idea as the CF card can only stand a certain number of writes before it eventually "wears" out (the paging file alone will destroy the CF as it constantly writes to the disk (CF)). XPe does not write to the flash (CF or DOM or DoC) as it uses a ramdrive.
The RAMDRIVE size can be changed in the Wyse build as I recall, in a control panel.That does not mean that applications cannot be added (depending on flash capacity) AND ramdrive capacity by disabling the EWF (or FBWF) and re-enabling (commit) after they are installed.
Unfortunately:
(a) the ramdrive size cannot be changed as it is set during the image build phase
Sounds like you know what you need to do, I'm just try to learn what I can through listening to the descriptions of others' projects. Here's one thing that I wonder about with the driver-matching business - how is it you can boot any x86 PC from just one floppy holding code that was written 15 years ago, if having exact drivers is needed? Doesn't that mean there is core functionality that is common to all x86 mobos that at least permits them to boot and run, even without vendor drivers? That may show how little I really know, but that's where I am.(b) I would need a working XPe image (one that boots on my platform) before I can add ("stuff") additional drivers and applications which was why I posted in this forum for (Ref: My post Mon Jan 30, 2012 7:52 pm).
So why not install XPe on a working platform and build my own image from drivers etc from VIA? XPe is now EOL and most importantly, MS dictates it being used only by OEMs.
Hope that clears up your questions.
I may just go Linux (ThinClient or TS-O-Matic for the image) but it will not run MJ unless I install a VM or Wine which not only defeats the purpose of
Linux (it's like scratching your right ear with your left hand - could have used your right hand in the first place!), but MJ has serious performance hits in running in a VM like latency, etc. Pure Linux TC's can run MJ only through RDP which again defeats the purpose of having a standalone MJ headless unit.
I need to think about it or experiment with a bunch of prebuilt XPe images. Unfortunately, I cannot contact Maxspeed Corp as they are defunct, and I cannot contact RETEK (OEM who built my image for Maxspeed) as they are also defunct even though I have the COA etc of original XPe image.
One other thing that I have tried to understand - how Wyse locks their units against cross-imaging. Somewhere the box and image conspire to decide whether they are authorized to pair up. You can't install their VX0 XPe image on their VX0 Linux or WinCE boxes for instance, even though they are identical hardware (you can take the XPe flash from the V90 and it will run any of the others like the V50 or V30, you just can't image them directly with XPe). If your TC does something similar, or if this functionality resides in the image build, launching the linux process might not work, is that right? Maybe what you're talking about is different than the linux-based process I see when the standard imaging is under way. Anyway, when I first read your post, I had thought you would parse the Wyse image file for the real meat, then use some other imaging means to get it onto your flash.
The key is understanding XPe so here's a link on the basics of why DOS "can boot without specific drivers" (still needs scsi, etc) and why Win XP can boot from a CD-ROM (it has all the basic drivers it needs (see boot up messages on install). To compare apples to apples you may want to refer to:
Building Devices Using Windows XP Embedded Lab from https://www.facultyresourcecenter.com/c ... 2=0&Login=
I'm sure there are other XPe resources if you Google'd for them but Sean Liming is one of the better known experts out there.
or take a look at slide 24 (TAP (Target Analyser) - https://www.facultyresourcecenter.com/c ... 2=0&Login=
If you really wanted to delve into XPe, you could read "Windows XP Embedded Advanced - By Sean D. Liming"
"how Wyse locks their units against cross-imaging" - most OEM's now use BIOS tattoo(s) - a work around is OEMBIOS and then dd the image
Building Devices Using Windows XP Embedded Lab from https://www.facultyresourcecenter.com/c ... 2=0&Login=
I'm sure there are other XPe resources if you Google'd for them but Sean Liming is one of the better known experts out there.
or take a look at slide 24 (TAP (Target Analyser) - https://www.facultyresourcecenter.com/c ... 2=0&Login=
If you really wanted to delve into XPe, you could read "Windows XP Embedded Advanced - By Sean D. Liming"
"how Wyse locks their units against cross-imaging" - most OEM's now use BIOS tattoo(s) - a work around is OEMBIOS and then dd the image
Don't think he can make these thin clients any more...
I build computers, and the parts for these thin clients are being blocked by some kiosk developer companies. Patents are owned by a handful of companies that develop micro-form-factor and kiosk terminal computers, and are policed by their lawyers.
Especially Microsoft's, which frowns on the distribution of Windows XP without genuine COAs assigned to the manufacturer. He could be tied up by a lawsuit that prevents him talking to us about the possible suit against him.
I know the MJ Plus now defeats the purpose for these thin clients, but they have many other useful applications.
Especially Microsoft's, which frowns on the distribution of Windows XP without genuine COAs assigned to the manufacturer. He could be tied up by a lawsuit that prevents him talking to us about the possible suit against him.
I know the MJ Plus now defeats the purpose for these thin clients, but they have many other useful applications.
Robert P Roehm
Re: Don't think he can make these thin clients any more...
I'm not sure that the MJ+ has made the MJ Thin Client (TC) obsolete - as a matter of fact the TC can still be used with a wireless PCI adapter in the expansion slot (I'm talking only of the Neoware and Maxspeed TCs I'm familiar with) and have a telephone station without having to run telephone wires from the MJ+ / Router to maybe the guest bedroom. I did go this route (my router is in my basement and my home office on another floor) and it's far less expensive especially if the telephone is on the opposite side of the house.macrat wrote: I know the MJ Plus now defeats the purpose for these thin clients, but they have many other useful applications.
I haven't tried a USB Network adapter on the TC but I'm sure it will work - depends on how much space the USB drivers (and maybe a setup program bloat) would require on the DOM or CF card.
Alpman had managed to integrate both the Maxterm and Neoware architectures in his uDrive images. I need an 256 Mb XPe SP2 image for a Maxterm 8300 Thinclient - the Maxterm uses a Compact Flash not a DOM. Anyone have one to lend/spare/sell? I would prefer a 256 Mb CF image with XPe SP2. Or anyone know how to modify an existing HP T57xx or Wyse XPe SP2 256 Mb image for a 256 CF?conniemadagain wrote:YUP ... I still have mine from alpman w/upgraded memory ...
guess i should sell it ...
:lol:
Connie/Stxfarmer - Any help would be appreciated since Alpman hasn't surfaced in a while.