- This topic is empty.
-
AuthorPosts
-
February 24, 2007 at 8:49 am #289
Hi,
I am using the new version of WDM 4.5.1 and was trying to pull the VX0 Dual Video Thin Client image through it. WDM prompted me error “FAILURE (OR NO ARCHIVE)”, WDM 4.5.1 does not fully support the VX0 DV Thin Client.
If you have any Hotfix for WDM 4.5.1 which will support VX0 DV Client, so give me the link of it.Regards,
EnamFebruary 25, 2007 at 10:06 am #9089Hi Enam,
I have not tested a new V Dual with WDM 4.5.1 and I would have expected full support. Let me do some testing and see what I come up with,
Cheers,
-TTFebruary 26, 2007 at 9:47 am #9098Quick update – I tested WDM 4.5.1 with a V90 dual video and it imaged without any problems.
Have a look in you intetpub/ftproot/rapport/tools/sa for the VL products and make sure all the .i2c and .i2d files are there,
Cheers,
-TTMarch 1, 2007 at 4:00 pm #9140Hi,
Thanks for your given me update, In future i will be need your further assistance. I will check to reflash again the VX0 Dual Video Thin Client using WDM 4.5.1.
I successed to pull the VX0 Dual Video Thin Client image using WSI version 1.1.5. Your Tech Docs named “Creating Images with Wyse Simple Imager” helped me to create image.
I will use the WSI 1.1.5 VX0 DV Device templete for WDM 4.5.1, I hope it will give me success.Cheers,
EnamMarch 8, 2007 at 3:36 pm #9191Hi,
Now my WDM 4.5.1 is working for VX0 Dual Video device using WSI 1.1.5 device script. Now I can get all the VX0 Dual Video device image. 🙂
Cheers,
EnamMarch 9, 2007 at 4:53 pm #9203In the folder for the VL (9V92) for XPe there are a couple of .i2c files (push and pull)
Depending on what command you are trying to accomplish, try opening the .i2c with notepad and modifying the =YES to =NO
The pull.i2c would be the same but with PULL_HOSTNAME
I’ve had success with this when the hostname.arc gets corrupt or is missing.
-k
-
AuthorPosts
- You must be logged in to reply to this topic.