Actually I am having second thoughts about updating the video driver.
I have on app which crashes my XP and the WndDbg indicates problem with video driver.
But - only one app has this problem, so logically it points to the app not liking this particular driver.
So I would not want to kill my whole PC for this stupid app problem.
<pre lang="text"> Up font, I can reload it if necessary, but I HAVE to ask this stupid question.
I did clean install of XP from my original CD, but I did not have the internet connected.
And I really did not pay much attention to the process.
But it started and worked OK.
Now I have spare PC, currently not reassembled ( no keyboard or monitor) and no access to internet.
The $64 question:
Do I have broken network interface ( the PC was a"gift") or should I have internet plugged in during the install?
Or should I put it back together and let Device Manager find the network interface
with the live network plugged in?
Thanks for reply.
The "problem " is the NIC driver was never installed and I am not sure about the motherboard hardware.
I tryed two drivers per manufacturer spec but neither one of them would start the NIC.
As soon as I figure out how to access / change / add password to my internet wireless "modem / router " I'll try to connect the new PC to the internet that way.
Since I have never used the wireless part it is another search for me, but I got the USB dongle connection working!
The "problem " is the NIC driver was never installed and I am not sure about the
If there's no network adapter mentioned in the device manager, then it's not installed.
If it's plug and play hardware, your best bet is to hook it up to a system with an active internet connection. Add it to the system, not the manufacturer and model once it gets installed, then search Google for an offline installer.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
I found one, do not recall the name /type , but it would not start.
I guess I could go back and remove the two I have added and note the one which is in there.
I really suspect it is broken.
But I need to learn how to work with the wireless adapter, so I ma taking that route for now.
I posted this in the now-uninhabited RootAdmin site, but I don't really expect a response and hope for better here. To wit:
At work we have a local network with 15 or so PCs and a couple of network printers connected to a 24 port switch, thence connected to the outside world via a SonicWall firewall. Since the SonicWall includes several VPN licenses, and I often travel, I thought it would be a snap to construct a protected tunnel from my Win7 laptop to the SonicWall, effectively connecting me to the edge of the network and enabling me to browse and use any of the local network resources.
I had our IT guy set it up for me for my last trip out of town, and I fired it up from my hotel room. All I could see in Windows Explorer was a single Shared folder - nothing else was visible. I checked with the IT guru today and he told me that I could connect to anything I want to, so long as I know the IP address or network name, but that it's impossible to set up the VPN to support browsing and a Network Neighborhood-style view on the remote computer.
I don't think I believe that, but since I haven't worked on PCs and networks for a living in about 10 years, I haven't kept up with what MS has been doing to make life less convenient lately. Can someone familiar with using and configuring VPN connections confirm or deny that what I want to do is possible? Better yet, can someone tell me how to set it up? If it matters, we have servers on the network, but we aren't configured as a domain and don't use Active Directory.
One thing I have done in similar circumstances is to VPN into a "client" PC on the LAN, and effectively inherit its view of the local network. It's a while ago now, so I'm a bit hazy on the details. Effectively running remote desktop off an "inside" PC.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
Hm, not sure about that browsing experience, as I normally don't use it.
I can access network shares in a different office (which are mapped to some drive letters) by clicking on them in the Windows Explorer - and only then will their state change from offline to online, and when accessing internal websites, the addresses are already stored in the bookmarks of the web browser.
Here in a branch office, network browsing in Windows Explorer only shows computers of this office, it does not show computers at other offices, though I can access them as described above.
[Edit]Now working from my hoem office, I see only one computer when browsing the network: mine. So everything looks OK.[/Edit]
Since the SonicWall includes several VPN licenses, and I often travel, I thought it would be a snap to construct a protected tunnel from my Win7 laptop to the SonicWall, effectively connecting me to the edge of the network and enabling me to browse and use any of the local network resources.
I have a couple of clients running SonicWALLs. Are you connecting in via the Global VPN Client? That is how I connect in from the outside world and when doing so always RDP to a computer on the remote network to do my work from.
One of the clients has several offices and they are connected voa Site to Site VPN. On those networks I can access anything as if it was on the local network.
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
We're using the VPN Client from Dell, but I don't know if it's the Global version - SonicWall invents their own terminology, and I've never found it easy to break the code. I've had the IT guy change the setup, and I now use a VPN to connect to my PC at work via Remote Desktop, then browse from there. It's working great, and much to my surprise, isn't significantly slower than sitting directly in front of the work machine.
There used to be a couple of hacks from Microsoft called CConnect and LimitLogin[^] that came with Windows 2000 resource kit. I have some doubts that it works on Server 2008.
Another solution is of course to use Remote Desktop.
This is related to software licenses (without a license server (*)) bound to a user name (i.e. only user "Joe" can use the software); this means that "Joe" could log in on different machines and use the software.
Currently, we generate licenses bound to some hardware keys (NIC/HardDisk); so if the machine dies we have to generate a new license (and that bugs a potential client that we really want to have) and they have to get back to use to generate a new license.
(*) We already use hardware USB license key; and will probably look into a proper license server (like flexlm).
I was looking for a confirmation if that was allowed on Windows or not.
Depends on what the local admin allows on his network.
You'll need a server (under your administration), it's that simple. Either one that's online, or on-site. Could be a cheap Raspberri Pi in a lockable box. Then you could have each client tell that server when it is online, and under which user. If a user is already online, simply tell the second instance (over TCP/IP e.g.) that it should shut down. Encrypt your connection and include a timestamp to prevent people from recording and playing back sessions.
Also be sure to implement a heart-beat to your server; that's the easiest way to detect when a connection is dropped, or a process died.
See, access to your application can be blocked; but blocking the machine would be considered a hostile act
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
Check underneath [(HKLM/HKCU)\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\StartupApproved\(Run/RunOnce etc.)] and corresponding entries under Wow6432Node.
Seems like a binary entry of "02 00..." means that it's enabled. The disabled entries is a bit more in a disarray though.