This patch enables your Windows Vista Machine to allow concurrent remote sessions.
I've made this patch using various hacked termsrv.dll's found in various forums like Neowin and OSNN. Hence credit goes to them.
Related
Hi all,
Having a lot of problems trying to use a VNC server on my Vario 3.
I've installed PocketVNCServ 0.8.1-EN from pocketvnc.sf.net and its running listening.
Whenever I try to connect from my desktop to it (I've checked and the IP for my Kaiser is correct), and every time I get:
Code:
vncviewer PreferredEncoding=raw ZlibLevel=0 AutoSelect=1 169.254.2.1
VNC Viewer Free Edition 4.1.1 for X - built Sep 10 2007 17:17:04
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Wed Dec 5 10:36:43 2007
CConn: connected to host 169.254.2.1 port 5900
CConnection: Server supports RFB protocol version 3.5
CConnection: Using RFB protocol version 3.3
TXImage: Using default colormap and visual, TrueColor, depth 24.
CConn: Using pixel format depth 6 (8bpp) rgb222
CConn: Using raw encoding
main: write: Connection reset by peer (104)
I've tried quite a few different connection parameters, auto detection, etc and none seem to work. I'm guessing its not matching the capabilities of the screen/resolution or something and giving up, can anyone give me a clue where I'm going wrong please?? I desperately need to get this working, and since I'm running under Linux cannot use the activesync solutions out there.
Cheers!
Andy
Do u have real vnc enterprise on the computer? They are really compatable with eachother. But idk about linux, works fine on Vista.
THis doesn't answer your VNC issue, but have you tried mymobiler.com ? Cool app (but for Windows, so you could try running it via Wine or in a VM session on Linux).
MyMobiler installs on Windows then on your next sync will install and connect to your phone. You can then pull your phone screen right up on your PC and control it as a window in Windows. Very handy.
I'll see if I can source vnc enterprise, but wasn't aware of any protocol differences between the software packages, something you're aware of?
And, unfortunately wine/crossover won't work with Activesync at all, due to many issues, so that isn't a possibility at present.
ekw, any chance you could enable debugging on your windows vnc client and see what encodings, screen resolution, etc it uses and I'll try to shove those settings into my vnc client by hand and see if it solves the problem??
ekw said:
Do u have real vnc enterprise on the computer? They are really compatable with eachother. But idk about linux, works fine on Vista.
Click to expand...
Click to collapse
No need for that - it works just fine with the free (!!!) TightVNC client, as has also been explained in http://wiki.xda-developers.com/inde...y) Pocket PC from another (desktop) computer?
BTW, as far as MyMobiler (and other alternatives) are concerned, I really recommend thoroughly reading the articles at http://wiki.xda-developers.com/inde... from both the desktop and the mobile device) - I've VERY thoroughly compared all these solutions to each other. ALL your questions will be answered in there.
Hi,
thanks for that, I'd already studied the wiki documents several times, and none referred to Linux compatibility, so was basing it around the TCP/IP methods.
It looks like the linux vnc clients operate very slightly differently to the Ultra/TightVNC clients for windows, as I tried this on a friends laptop and got a connection and remote control immediately.
So i used Crossover/Wine and installed UltraVNC to my kubuntu desktop, and sure enough that connected up and works fine.
I'll do some debugging to find what differences there are, as I should be able to easily use native linux VNC clients (its a transfer protocol underlying, so shouldn't be a compatibility problem).
So, I'll post back with further details as I'm sure others will want to do what I've been doing under Linux, as we're not all windows clones on our desktops ;-)
evening gents and lady
i have a query for chefs mainly but anyone with OS knowledge can help.
basically i work for a company that recycles computer equipment, we receive a lot of certain models mostly the dell optiplex gx range. and rebuilding them entails we have to install the OS from the oem discs and then preceed to either download drivers from dell, install from out in house servers or usb pen drives.
i had a thought that maybe the drivers could be installed as packages onto the disc a bit like windows mobile.
ideal situation
One master disc with the operating system on AND all the drivers for the range os systems we build. in this case xp w/ sp2 then after the normal os installation i want a program maybe to detect the model and install the drivers that are on the disc automatically. a bit like the app that installs opera and google maps on coked rom (UC?) also if that goes well i can then include all the apps that we install like ms security essentials. open office etc
is there anyway to do this
have you got a dell oem disc?
I have and it installed the driver auto
flyboy
we have a standard oem disc that does all of our models but thedriver needed differ from machine to machine for instance sometimes the ethernet adapter gets installed by default other times we have to install it after the main os insta;ll
There is a way to do it. Few questions:
1) What Windows O/S
2) Do you have an OEM product key
3) Are you familiar with slipstreaming
* EDIT *
Guess we posted at the same time. You need to slipstream the drivers into the O/S media. It's not usually best practice to included applications but can be done. Depending on the version of Windows, a final post config exists to trigger silent installs of extra applications. It's all part of a SYSPREP deployment process.
we use dell oem disc xp with sp 2, the keys do not have to be written in on the setup and no i dont have a clue what slipstreaming is
-PiLoT- said:
we use dell oem disc xp with sp 2, the keys do not have to be written in on the setup and no i dont have a clue what slipstreaming is
Click to expand...
Click to collapse
In slipstreaming you can place your drivers into the OS so on install everything is done. "including stripping system components integrating service packs"
XP nlite
I just have a library of about 9000 drivers on a CD that always lives in me bag. "and stored as ISO image on computer" These compilations can be found online.
The choice you choose will depend on if you have a quantity the same then you can use nlite as you know the install the same or just bung all drivers onto a disk
The process you're after is a sub-process of imaging.
Here's an abridged version, very abridged, but should give you a sense of what's involved ... having done this a few (aka many many) times.
Media
Generally, the media to use for this type of activity is obtained directly through Microsoft as using another OEM's media is generally problematic as it has been altered for their requirements. Since you're using the DELL OEM CD on DELL OEM systems, you can "get away" using it.
One of the steps you may want to do is slipstream WinXP SP3 to the media. Here's a good site to get you on your way, there are many more out there:
http://www.winsupersite.com/showcase/xpsp3_slipstream.asp
Product Key
The product key embedded in the OEM CD ensures that it is only useable on DELL branded equipment. This permits end-users to rebuild their system and skip the product activation phase - the caveat being that OEM media is used on the OEM system; you can't interchange OEM media/systems as this will trigger activation.
Enterprises usually obtain a Volume License Key (VLK) which allows them to use imaging methodologies to deploy the O/S to workstations.
Note
Before others chime in ... yes, there are "work arounds" but since we're sticking to legitimate usage - we'll avoid that topic.
Pre-Delivery Process
There are two approaches to this process.
The first, traditionally used by OEM's (ex: DELL, HP, etc.) is to inject their drivers into the O/S media and modify some of the setup information files so as to ensure that the drivers are detected during the TEXT & GUI setup portions of Windows.
The second, traditionally used by Enterprises (ex: 20+ workstations) is to build a base image which is: install windows, install drivers, run SYSPREP, capture (seal) image. Knowledgeable IT builders will usually inject the drivers they require and adjust the setup information files prior to running SYSPREP and "sealing" the image.
Note
Large OEM's will also use the second process so that they may build many similar systems at once for shipment purposes. In a nutshell, the customer gets the media but the actual system HDD has been imaged.
Additionally, some OEM's will ship their systems with a hidden partition that is accessible by pressing a combination of keys at boot. The hidden partition contains a copy of the system image which can be restored to the visible partition.
Post-Delivery Process
The are two approaches to this process.
The first, traditionally used by OEM's (ex: DELL, HP, etc.) is to provide the O/S media along with the system. At the factory, an image is copied to the system HDD (see note above) and the system is shipped to the customer. When the customer unpacks and starts the system, the mini-SYSPREP is initiated and the system goes through a mini-GUI setup procedure.
The second, traditionally used by Enterprises (ex: 20+ workstations) is to take the pre-delivery process "sealed" image and upload it to a distribution system such as SMS, Altiris, OnCCM, Symantec GHOST, etc. The BIOS of the workstations are usually configured so that the Network Adapter (NIC) is set for Pre-eXecution (PXE) boot. A Wake-On-LAN is sent to the MAC address of the workstation (which has been recorded during asset receipt/delivery), the workstation turns on, sends a PXE-Boot request, the DHCP server responds to the request and forwards the request to the distribution server, the workstation receives a boot image from the distribution server, which in turn initiates imaging of the workstation HDD. Once completed, the workstation reboots and goes through an automated mini-GUI setup which performs all of the necessary detection and driver installation.
Some Final Points
You can inject drivers to the physical media (ex: Windows XP) and perform individual installs of Windows on a system-by-system basis. This is often referred to as slipstreaming drivers or injecting drivers. This is often required for AHCI controllers on new systems.
Imaging can be "tricky" if you have to deal with multiple variations of hardware abstraction layers (HAL) such as in the case with single/multi processor architecture.
Ensure that customers receive a copy of the media with their systems so as to remain compliant and not violate license agreement terms.
Avoid using NLITE unless your company is planning on providing continuous ongoing support with each system sold. NLITE is an extremely fast method of preparing systems for mass image distribution. Unfortunately, it is not officially endorsed/supported by Microsoft and/or OEM's. Enterprises or individuals can usually "get away" with using NLITE as they typically self-support their systems.
Recommendation
In your situation, it may be easiest to read up on the following methodologies:
Slipstream service pack to cd-rom (media)
Slipstream (inject) drivers to cd-rom (media)
HTH,
wow thx H
very concise. i think even though were technically classed as an enterprise. i think id still prefer to use the oem solution. looks like im going to have to have a disc per model instead of one master disc but cant win em all.
using nlite wont do as we only provide 3 months official warranty on the product
so i think my best bet is to copy the contents of the cd to a computer. then insert my drivers onto it the make a iso out of it then make a bootable cd. the customer wont get a copy of the edited cd. think they might have something to say having the recovery disc on a tdk cd/r
using the oem disc you have got. research on the internet and find out where the drivers are kept on the disc, then copy the disc to your pc and insert the drivers then burn to disc. this way the drivers would be on the disc.
read this as well. i think its a noob sort of guide to slipstreaming:
(cached google page)
http://209.85.229.132/search?q=cachedCEft9ToWQJ:tech.yahoo.com/blog/null/99108+where+are+drivers+on+xp+disc&cd=7&hl=en&ct=clnk&gl=uk
flyboy
( sorry just reaslised i have posted what you said, pilot)
Hello I am trying to figure out how to unlock screen rotation and reporting here about any progress on Windows 7 with intel GMA945/950
Note: many other users reporting on web that rotation is disabled on theirs intel GMA chipsets and different hardware.
This article is directly linked with Gsensor article that permits display rotation using integrated g-sensor on our devices (WinXp only right now).
http://forum.xda-developers.com/showthread.php?t=673942
After a bit of searching in .inf file seems that Shift's driver lacks some configuration so I am using Gigabyte m912 drivers (v.8.15.10.1930) you can find it by the link above
http://www.gigabyte.com.tw/Support/Notebook/Driver_DownloadFile.aspx?FileType=Driver&FileID=4489
Then I've found this article and merged missing registry keys
http://forum.tabletpcreview.com/133851-post30.html
Unfortunately with no positive results so far.
I will continue my tests,if any other will join please report here your results.
Keep trying!
Im not surprised to see the intel graphics drivers at fault. The HiRes>LowRes aero turn off isn't HTC's problem its the Intel drivers only their control panel can switch back without turning aero off everything else including Windows and the API to change resolution experiences the problem above.
Thanks for providing the alternate drivers ill take a look aswell.
I was about to update multiple projects to be compatible with WP 8.1 when I hit multiple snags.
One of those is: Type.IsAbstract is missing in WP8.1 apps (I'm talking about the real wp8.1 apps and not Windows Phone Silverlight 8.1 apps)
Now since my project I want to convert is a portable class library that is currently targeting - .net framework 4.5, Silverlight 4 and higher, Windows Phone Silverlight 7.1 and higher, Windows 8 - I was expecting a relatively smooth transition.
When I was experimenting with different PCL targets I found a workaround for the missing Type.IsAbstract but I can't imaging that to be the correct way of testing if a type is abstract or not:
When you specificly target the following frameworks in pcl: .Net Framework 4.5, Silverlight 5, Windows 8, Windows Phone 8.1, Windows Phone Silverlight 8, then Type.IsAbstract is available in this project and therefore you can write a function to test if a type is abstract and then use that function in a Windows Phone 8.1 app to test if a type is abstract (or simple create a extension method in the pcl).
It works, I tested it. It seems really strange, especially because when you REMOVE Silverlight 5 from the pcl, Type.IsAbstract is not available anymore in the pcl project.
I'm asking because I can't use these specific pcl targets (or more exaclty I can't have Silverlight 5 as a target) because then ObservableCollections are not available and there is no Json.Net (Newtonsoft) target for these pcl targets.
(It would mean splitting my lowest project into two projects and my self written framework already consists of 25 projects)
Ok,
after some testing I found a solution.
In WP8.1 and seemingly in all relevant (at least for me) PCL targets that include WP8.1 you have to add:
Code:
using System.Reflection;
Then you have multiple extension methods available for "Type".
Relevant in this case is "GetTypeInfo()" which then includes "IsAbstract"
and in my case many other methods I need ("GetRuntimeProperty" and more)
Was reading some stuff on:
no allowed to post links msdn(dot)microsoft(dot)com/en-us/library/dn715933(v=winembedded.81).aspx
Windows 8.1 Embedded Handheld is basically Windows Phone 8.1... but then we got:
"ID_CAP_ENTERPRISE_SHARED_DATA"
It's replacing the "ID_CAP_INTEROPSERVICES" in enterprise apps... I'm just wondering if you need an Enterprise/OEM developer account to use this cap? Anyone tried anything with this and deploying it to Windows Phone?
No time currently to test anything, was reading about this during a train ride...