Forum Replies Created
-
AuthorPosts
-
Hello jmccammond,
you may block the UDP-Ports 67-69 (if not needed for dhcp) on the WAN connection. This will inhibit a PXE (TFTP-Transfers) over the WAN-connection, but this means you may need a second dhcp-server on the other side of the WAN.
If you really use PXE forwarding over a WAN Connection, please keep in mind that PXE (not the later ftp-Transfers) use TFTP as protocol. TFTP is a simple connectionless network protocol. If there is a error (e.g. timing transfer error) there is no way to re-transfer the missing block. I would not use TFTP over WAN-connections at all.
Peter
Hello
for latest driver check these websites with your OS and the chipset of the winterm client:
V30: VIA CN700 Chipset
http://www.viaarena.com/default.aspx?PageID=2&Type=23150: AMD Geode GX chipset
http://wwwd.amd.com/AMD/SReleaseF.nsf/softwarepages/DriversByOS?OpenDocument3125: AMD Geode GX1 chipset
http://wwwd.amd.com/AMD/SReleaseF.nsf/softwarepages/DriversByOS?OpenDocumentPeter
Hello Fidl4000,
the actual video drivers for Windows XP Embedded SP2 and the VIA CN700 UniChrome Pro integrated graphics (V90L) can be found here:
http://www.viaarena.com/default.aspx?PageID=420&OSID=24&CatID=2500&SubCatID=158These drivers are from March 2006.
Just as a remark, for the V90 (witch has PM880 chipset) newer video drivers exists:
The actual video drivers for Windows XP Embedded SP2 and the VIA PM880 UniChrome integrated graphics (V90) can be found here:
http://www.viaarena.com/default.aspx?PageID=420&OSID=24&CatID=2500&SubCatID=110These drivers are from April 2007.
I don’t know if the video driver for V90 will work on V90L terminals since PM880 is a older chipset. Normaly I would not advice to use a driver for a different Videochipset
Peter
Hello Fidl4000,
the links on the wyse site are dead (page not found html page saved as zip file). Since the Wyse V90L has mainboard with via CN700 chipset look for the embedded drivers at VIA’s Arena website at http://www.viaarena.com or google for XPe and CN700.
Peter
Hello El Honcho,
I guess you solved your problem. Just as a remark for those who search for a solution to a simular problem:
At this forum I opened a thread, to get the missing options needed for getting the Wyse Simple Imager (WSI) running.http://www.freewysemonkeys.com/site/modules.php?name=Forums&file=viewtopic&t=560
Peter
August 29, 2007 at 9:13 am in reply to: Problem with installation of WSI (Wyse Simple Imager) #10098Thanks Thomas,
this was the missing part. I filled in Option 66 and 43
I had to fill in Option 43 in hex, so this hexcode reads like:
3C 04 49 54 46 00 43 09
72 6F 6F 74 2E 69 32 75As ascii text this reads similar to: ‘< ITF C root.i2u '
Just to complete documentation, here is my full wnos.ini:
autoload=1
Fileserver=10.1.1.12
Rootpath=/$
Rapportserver=10.1.1.12
SignOn=NoThank you for your assistance. I guess without your support I never filled in this hexcode to option 43.
Peter
August 29, 2007 at 7:44 am in reply to: Problem with installation of WSI (Wyse Simple Imager) #10096Hello ConfGen,
10.1.1.12 as descripted in standard setup expample
Peter
August 29, 2007 at 5:53 am in reply to: Problem with installation of WSI (Wyse Simple Imager) #10090Hello Conf Gen,
067 Value is rapportitf.0 and PXEboot-Agent starts as mentioned above (…This will start a pxe bootimage with the WISard 4.4.02 PXE Agent…)
Peter
August 28, 2007 at 3:25 pm in reply to: Problem with installation of WSI (Wyse Simple Imager) #10080Hell Conf Gen,
* W2k3 Server is installed in german
* The environment is isolated (just a cross-over cable between V90
and server)
* DHCP Server is from MSDHCP Options we set are:
003 Value:10.1.1.12
015 Value:10.1.1.12
043 Value:0
067 Value: rapportift.0
161 Wyse FTP Server (Value: 10.1.1.12)
162 Wyse FTP Folder (Value: /$)Peter
-
AuthorPosts