- This topic is empty.
4. June 2008 at 14:28 #1247FavordaveMember
- Total Post: 3
I have an issue very similar to the resolved topic found at http://www.freewysemonkeys.com/modules.php?name=Forums&file=viewtopic&t=1086
The the solutions however did not work for me.
I bought a lot of 8 old WYSE’s. Some of them are labeled WT8360SE, 2 are labeled as 3360SE’s. Regardless of the box, they seem to behave exactly the same. This is the boot process:
Flash memory verification
Then the only thing that would come on is the billgPC 2.06
It would successfully find my router and says received Valid BOOTP Offer as precious topic did.
Then just as the previous post, it would then have an error message of “Cannot connect to the the RDP server.” Once that message box is closed, the I would have a blank desktop with nothing on it. The only keystrokes that would have any effect is the Alt-Ctrl-Del combo which gives me the option to shutdown or restart.
I have tried to used XFER and all available bin files for either devices from Windows 98. Whenever I do that, the devices would simply get stuck at the splash screen withe the computer stuck at Waiting to Download…
I have been struggling with these machines for more than a weeks now. Any little help would be greatly appreciated.4. June 2008 at 23:14 #13171
What image were you trying to load? Try and use the CE based 3360 images first,
-TT5. June 2008 at 16:15 #13181FavordaveMember
- Total Post: 3
I tried all the images availble on the WYSE website for both devices.
That’s 506.4Wye1E, 506.4Wye1F, M64STD182.bin, M64STD183.bin and M96STD182.bin. All with the same result, the Windows 98 computer stuck at Waiting to Download and the terminal at the splash screen.6. June 2008 at 11:36 #13187
Hmm, not sure here. These units sound like old Wal Mart units with the Wal Mart code. One other user of the forums had the same issue and was eventually able to load CE2.12 code on them. You tried 506 code but I winder if this is too new and too big.
Let me find some older CE 2.12 code and post it for you,
-TT16. June 2008 at 20:03 #13260
We are having the same issue with this exact same model – WT8360SE.
Like the previous reader, we have also tried using xfer to load the image from wyse – http://www.wyse.com/serviceandsupport/support/dlOraFW.asp?which=47&model=8360SE
When loading the smallest of these images (63,547KB), we get 93% of the way done and then it fails – out of space.
Our next step was to obtain a working model and then use nte extractor to get a good 8360SE image we could use to deploy to the lot we purchased.
If you have an alternative image for these devices that will work with xfer or nexfer we would also love to try it.
Any help would be greatly appreciated.16. June 2008 at 20:08 #13261
There is also this: http://www.panix.com/~perin/
It’s about a bootp client. I haven’t explored trying this method yet, especially as it appears like we have an image problem, not a transfer problem.25. June 2008 at 7:35 #13338
Here is the CE 2.12 code for the 3360, see if you can load this with Xfer and then upgrade to a newer CE version from there:
-TT5. July 2008 at 19:00 #13431tenwisemanMember
- Total Post: 3
I’ve got a theory that there must have been a 48MB NTe image available at some time. My 8360SE has 32MB flash soldered on board, and 16MB in the ‘CF’ socket. Mine is Part No. 901996-12 & I’ve lost my image 🙁
If I were to come across someone with a working NTe in 48MB flash could the image be extracted?
Sorry, beginner to some of this!
Adrian C6. July 2008 at 9:01 #13433
I will check out what old files I have….7. July 2008 at 0:29 #13435
OK, so this is what I have found out so far….
Apparently there are a load of special build 3360SE Wyse terminals that were sold to Walmart which are floating around ebay now. These devices either had CE or a special build of Windows NTe. The NTe build was very small to fit on to the CE sized flash units.
This leaves you with a problem, these units have a Card Flash expansion slot that only has a 16MB flash card which is not enough to load the standard build NTe from Wyse. Also those with the Walmart build will find there is not enough space to load much up anyway.
So what are the options?
Load the CE 3360SE build to the units, as they have 48MB of flash space (32MB on board and 16MB on card flash) you should be able to fit a CE4 build.
Next (expensive) option is to use a 32MB Card as card flash. Its not that simple as these units only take some cards (Linear Flash AMD, Centennial up to 32MB). Getting these cards now days should be, well interesting.
If you are a Linux Guru I guess you could load a tiny Linux distro, there are a few sites on the net that post around converting old Wyse devices.
One other note, I found this bit of info that claims the BIOS in the Walmart units is converted to use netXfer not Xfer, this means you would have to use cross over cable and netXfer to load a Wyse image NOT a parallel cable like on all other 3360SE units. Here is the note:
“This build contains the NetXfer for 8360 BIOS. Once this build is applied to an 8360, you can no longer flash the terminal with a flash card or parallel cable. Only NetXfer can flash the terminal. Included with the build is a CE 3360 build with the same BIOS. To re-flash your 8360 back to standard build, use the CE build with NetXfer to deliver the CE build to the terminal. Then use the CE build to pull down a standard NTe image.”
So I would try this and see how it goes, I hope this info is useful,
-TT7. July 2008 at 17:13 #13447
ThinkThin, thank you immensely for all the research you’ve done and for providing the information regarding the history of these particular devices.
I went over to WYSE and found the following downloads for the 3360SE:
I’m going to try and load the smaller image this week with netxfer and see if I can make any progress.
If anyone else with these winterms has success, please post to this thread.7. July 2008 at 23:03 #13451tenwisemanMember
- Total Post: 3
ThinkThin, thanks very much for your contributions as well 🙂
On my 8360SE I’ve managed to xfer/laplink across the bin file in the 506-4Wye1F_3360_FTP_CEN folder in the file “506.4Wye1F_3360_FTP.exe”, and it’s up and running CE.NET 4.2 fine. Well, I might keep it like that – the RDP stuff seems to work OK on that CE build, and I’m now looking at the addons I can put with WyseDeviceManager (If I can get a workgroup key for it)
IVDesk, could you share with us the part numbers of your unit(s) please?
I’m in the UK so I don’t know what the odds of a Walmart unit turning up on these shores – I got mine from a car boot sale in a sorry state having the PCB covered in liquid hand soap. Luckily it washed off…
Adrian C8. July 2008 at 21:57 #13459
We’ve got about a hundred of these that we picked up on eBay.
Part numbers for a couple of them are:
901996-119. July 2008 at 22:16 #13483
Thanks god news!
WDM installs with the workgroup key but for one unit you can you use the ftp upgrade method to add extra Wyse add-ons. Check out the admin guide on the Wyse support site,
-TT11. July 2008 at 0:28 #13490
I can confirm that xfer works with these models. Netxfer is on them and it does establish the connection, but then I get an error during the image transfer. I have not pursued debugging the error I got with netxfer.
Many thanks to thinkthin and tenwisemen for their help in resolving this problem.
- You must be logged in to reply to this topic.