Newsgroups to the rescue, here is a workaround for being able to login as Administrator on a Vista machine NOT in a domain.
http://windowsconnected.com/blogs/jerry/archive/2006/02/22/1028.aspx
Steve
Newsgroups to the rescue, here is a workaround for being able to login as Administrator on a Vista machine NOT in a domain.
http://windowsconnected.com/blogs/jerry/archive/2006/02/22/1028.aspx
Steve
Here is an update on my adventure of installing the Feb 2006 CTP Vista build. I’m using a Dell Server with Virtual Server 2005 R2 installed. The host OS is Windows 2003 Enterprise RTM version. The built-in NIC wasn’t working and I added my own NIC (3Com 3C905TX-based Ethernet Adapter (Generic)). One of the issues I was having my Vista build wasn’t seeing the network. When viewing the Virtual Server 2005 configuration, this error was displayed
Unexpected error (0x80004005). The virtual network’s configuration information could not be retrieved. Microsoft Virtual Server could not complete the operation due to an unexpected error (0x80004005). A little Google magic and I found this thread. Click Here to view
There was a NIC available inside my Vista instance however it wouldn’t ping the default gateway. I found an issue where someone else had an issue with Virtual 2005 R2 and “3Com 3C905TX-based Ethernet Adapter (Generic)” I didn’t reboot the host OS after install Virtual Server 2005 R2. In summary is what I did to get this working.
After the install finished, I installed Virtual Server additions, the OS was very responsive. My Vista adventure continues.
Steve
by Steve Schofield
Download the application
This article shows how to update an application config file and have the new settings
take affect without stopping and starting a Windows .NET service. This uses
the System.IO.FileSystemWatcher class in .NET 2.0. This was not easy in .NET 1.0 or .NET 1.1
but only requires a couple lines of code in .NET 2.0. My “hello world” application monitors a website
on a periodic basis and record the results to the Event Log, Database or sends an email.
You can download the code to see how I implemented this in my application. I’ve included the Setup project to install the application.
Here is the code that refreshes the ‘appSettings’ section.
protected void fsw_Changed(object sender, System.IO.FileSystemEventArgs e) { System.Diagnostics.EventLog.WriteEntry(“Application”,”FileChanged:” + e.Name); ConfigurationManager.RefreshSection(“appSettings”); LoadConfig(); } |
To test this out, install the application on your machine and start the ‘AWebMonitorServiceCS’ service.
After the service is running, change the URL setting to a different URL. After so many seconds,
that is configured in the ‘Interval’ appSetting this will record the data in the Event Log.
There will also be entries in the event log showing the ‘awebmonitorserviceCS.exe.config’ has changed.
Sample event log text when the file changed
The description for Event ID ( 0 ) in Source ( Application ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: FileChanged:AWebMonitorServiceCS.exe.config. |
Sample event log text what URL is being monitored
The description for Event ID ( 0 ) in Source ( Application ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: http://www.aspdot.net. |
Good luck!
Steve
I’m passing this along as an FYI. For those who are trying to install vista 5308(Feb CTP) on Virtual Server 2005 and running into this error. “instruction at 0x1fee7a6d referenced memory at 0x0315bd0f (this varies) …. the required data was not placed in memory because of an i/o error status of 0xc0000010”. You are not crazy!
What I ended up doing was un-installing Virtual Server 2005 Standard edition and downloading the 180 day evaluation Virtual Server 2005 R2 edition. For some reason Vista requires or likes the R2 version. Here is the link to download the Trial version. The one thing you will have to “fake” like you are ordering the software before you can get the download link. Just pretend and go through the process, you won’t be charged anything. After installing the R2 version, the error disappear and was working.
In summary
Hopefully this will save you a few hours in trying to geek on the latest Vista build!
Steve