Tuesday, December 7, 2010
Thursday, December 2, 2010
Windows XP Setup Keeps Restarting
If you cancel your Windows XP setup while it is in process it will reboot and attempt to restart the installation.
Boot to something that will let you edit the Windows registry offline and clear the following keys:
HKLM\SYSTEM\Setup\SystemSetupInProgress
HKLM\SYSTEM\Setup\SystemSetupInProgress
There is also a key called 'UpgradeInProgress'
Boot to something that will let you edit the Windows registry offline and clear the following keys:
HKLM\SYSTEM\Setup\SystemSetupInProgress
HKLM\SYSTEM\Setup\SystemSetupInProgress
There is also a key called 'UpgradeInProgress'
Wednesday, June 16, 2010
Google Earth Installation - Error 0x80040905 on Vista/Win7
With credit to http://nonsenseinbasic.blogspot.com/2009/04/google-earth-installation-solving-error.html
I recently tried to install Google Earth on my Vista X64 setup, so I could play with Geotagging photos - unfortunately Google Updater kept failing the installation. On an attempt to manually install, the installer bombed out with the mysterious error 0x80040905. Helpful stuff.
On my machine the problem was to do with mapped network drives.
First I checked this webpage for advice - it might help some of you, but it wasn't relevant to my problem as I don't have any existing versions of Google Earth installed. Then I remember an issue with some Adobe installations which had given me a weird 'Invalid Drive' error in the past.
The solution proved to be the same one:
1.Run CMD as Administrator. (type CMD into the start menu, then right click on the CMD icon in the start menu and choose 'Run as Administrator')
2.Type NET USE - you should see a list of any mapped network drives, but they will probably be listed as Unavailable.
3.For each network drive, type the command NET USE M: \\SERVER\SHARE replacing the server and share as appropriate.
4.Just for kicks, type NET USE again to check that your network shares are now up and running.
5.Don't close the command prompt just yet, install Google Earth and everything should go OK.
The reason for this is that in Vista network shares are set up on a per user basis, and the installer is running as Administrator. For more info do some sort of google search like this one.
I recently tried to install Google Earth on my Vista X64 setup, so I could play with Geotagging photos - unfortunately Google Updater kept failing the installation. On an attempt to manually install, the installer bombed out with the mysterious error 0x80040905. Helpful stuff.
On my machine the problem was to do with mapped network drives.
First I checked this webpage for advice - it might help some of you, but it wasn't relevant to my problem as I don't have any existing versions of Google Earth installed. Then I remember an issue with some Adobe installations which had given me a weird 'Invalid Drive' error in the past.
The solution proved to be the same one:
1.Run CMD as Administrator. (type CMD into the start menu, then right click on the CMD icon in the start menu and choose 'Run as Administrator')
2.Type NET USE - you should see a list of any mapped network drives, but they will probably be listed as Unavailable.
3.For each network drive, type the command NET USE M: \\SERVER\SHARE replacing the server and share as appropriate.
4.Just for kicks, type NET USE again to check that your network shares are now up and running.
5.Don't close the command prompt just yet, install Google Earth and everything should go OK.
The reason for this is that in Vista network shares are set up on a per user basis, and the installer is running as Administrator. For more info do some sort of google search like this one.
How to change the Windows 7 Login Screen Background
Thanks to withinwindows for finding out this excellent feature.
Although this functionality was designed with OEMs in mind, it is pretty easy to turn on and off using regedit and some images lying around your hard drive.
First, a check is made to determine if the customization functionality is enabled or not. More precisely, a DWORD value named OEMBackground in the HKLM\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background key is checked. Its data, of Boolean type, defines whether or not this behavior is turned on, i.e. 1 for enabled, 0 for disabled. This value may not exist by default, depending on your system.
Afterwards, if customization is enabled, the primary monitor’s screen height and width are retrieved via calls to GetSystemMetrics. These values are used in the computation of the screen width (w)/height (h) ratio. For example, my desktop resolution is 1920x1200. The ratio, computed by the division of w/h, is 1.6:1.
The result of this computation is looked up in an internal table that drives what image to load on disk. Although I don’t have a large enough monitor to test, it appears resolutions higher than 1920x1200 will force the loading and zooming of an image of closest compatibility (i.e. same ratio, smaller image).
As this is an OEM feature images are derived from %windir%\system32\oobe\info\backgrounds. Like the registry value, this folder may not exist by default. The following files (sorted by width-to-height ratio) are supported in this folder:
backgroundDefault.jpg
background768x1280.jpg (0.6)
background900x1440.jpg (0.625)
background960x1280.jpg (0.75)
background1024x1280.jpg (0.8)
background1280x1024.jpg (1.25)
background1024x768.jpg (1.33-)
background1280x960.jpg (1.33-)
background1600x1200.jpg (1.33-)
background1440x900.jpg (1.6)
background1920x1200.jpg (1.6)
background1280x768.jpg (1.66-)
background1360x768.jpg (1.770833-)
NOTE: Images must be less than 256kb in size. Thanks for pushing me to investigate, Jay C.
The backgroundDefault.jpg image is loaded and stretched-to-fit when a resolution/ratio-specific background cannot be found. The other resolution/ratio-specific files are self-explanatory. If the background cannot be loaded (e.g. image physically too large, incorrect ratio, etc.), the default SKU-based image is loaded from imagesres.dll. You’ll see a Windows Server-themed grayish background in there, too, suggesting this functionality is not specific to client SKUs.
With credit to http://www.withinwindows.com/2009/03/15/windows-7-to-officially-support-logon-ui-background-customization/
Although this functionality was designed with OEMs in mind, it is pretty easy to turn on and off using regedit and some images lying around your hard drive.
First, a check is made to determine if the customization functionality is enabled or not. More precisely, a DWORD value named OEMBackground in the HKLM\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background key is checked. Its data, of Boolean type, defines whether or not this behavior is turned on, i.e. 1 for enabled, 0 for disabled. This value may not exist by default, depending on your system.
Afterwards, if customization is enabled, the primary monitor’s screen height and width are retrieved via calls to GetSystemMetrics. These values are used in the computation of the screen width (w)/height (h) ratio. For example, my desktop resolution is 1920x1200. The ratio, computed by the division of w/h, is 1.6:1.
The result of this computation is looked up in an internal table that drives what image to load on disk. Although I don’t have a large enough monitor to test, it appears resolutions higher than 1920x1200 will force the loading and zooming of an image of closest compatibility (i.e. same ratio, smaller image).
As this is an OEM feature images are derived from %windir%\system32\oobe\info\backgrounds. Like the registry value, this folder may not exist by default. The following files (sorted by width-to-height ratio) are supported in this folder:
backgroundDefault.jpg
background768x1280.jpg (0.6)
background900x1440.jpg (0.625)
background960x1280.jpg (0.75)
background1024x1280.jpg (0.8)
background1280x1024.jpg (1.25)
background1024x768.jpg (1.33-)
background1280x960.jpg (1.33-)
background1600x1200.jpg (1.33-)
background1440x900.jpg (1.6)
background1920x1200.jpg (1.6)
background1280x768.jpg (1.66-)
background1360x768.jpg (1.770833-)
NOTE: Images must be less than 256kb in size. Thanks for pushing me to investigate, Jay C.
The backgroundDefault.jpg image is loaded and stretched-to-fit when a resolution/ratio-specific background cannot be found. The other resolution/ratio-specific files are self-explanatory. If the background cannot be loaded (e.g. image physically too large, incorrect ratio, etc.), the default SKU-based image is loaded from imagesres.dll. You’ll see a Windows Server-themed grayish background in there, too, suggesting this functionality is not specific to client SKUs.
With credit to http://www.withinwindows.com/2009/03/15/windows-7-to-officially-support-logon-ui-background-customization/
Thursday, April 22, 2010
Restoring Autoplay to removable media
Start, Run, Regedit
In the registry, delete:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoDriveTypeAutoRun
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoDriveTypeAutoRun
Make sure that HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\CDRom\AutoRun has a value of “1.”
Download the Microsoft Autofix Repair Wizard from http://www.microsoft.com/downloads/details.aspx?familyid=C680A7B6-E8FA-45C4-A171-1B389CFACDAD&displaylang=en and run it.
Restart and try again.
In the registry, delete:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoDriveTypeAutoRun
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoDriveTypeAutoRun
Make sure that HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\CDRom\AutoRun has a value of “1.”
Download the Microsoft Autofix Repair Wizard from http://www.microsoft.com/downloads/details.aspx?familyid=C680A7B6-E8FA-45C4-A171-1B389CFACDAD&displaylang=en and run it.
Restart and try again.
Wednesday, April 7, 2010
Server 2003 NTFRS Error 13568
This is the only resolution to error 13568 that I've seen posted that mentions the fact that the key they are referencing does not exist and has to be created manually.
RESOLUTION
==========
[...]
To modify the default behavior, make the following changes in the registry
to
instruct FRS to handle the JRNL_WRAP_ERROR status automatically:
1. Stop FRS.
2. Start Registry Editor (Regedt32.exe).
3. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters
4. On the Edit menu, click Add Value, and then add the following registry
value:
Value name: Enable Journal Wrap Automatic Restore
Data type: REG_DWORD
Radix: Hexadecimal
Value data: 1 (Default 0)
5. Quit Registry Editor.
6. Restart FRS.
If these steps do not modify the default settings and the automatic
re-initialization is not turned on, you need to manually re-initialize the
replica tree. At a convenient time, make the following changes to the
registry:
1. Stop FRS.
2. Start Registry Editor (Regedt32.exe).
3. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup
/Restore/Process
at Startup
4. On the Edit menu, click Add Value, and then add the following registry
value:
Value name: BurFlags
Data type: REG_DWORD
Radix: Hexadecimal
Value data: D2
5. Quit Registry Editor.
6. Restart FRS.
MORE INFORMATION
================
For additional information about SP3 updates to the File Replication
service,
click the article number below to view the article in the Microsoft
Knowledge
Base:
Q307319 File Replication Service Improvements in Windows 2000 SP3
--
--Brian Desmond
Windows Server MVP
desmondb@payton.cps.k12.il.us
Http://www.briandesmond.com
Taken from http://www.pcreview.co.uk/forums/thread-1446618.php
RESOLUTION
==========
[...]
To modify the default behavior, make the following changes in the registry
to
instruct FRS to handle the JRNL_WRAP_ERROR status automatically:
1. Stop FRS.
2. Start Registry Editor (Regedt32.exe).
3. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters
4. On the Edit menu, click Add Value, and then add the following registry
value:
Value name: Enable Journal Wrap Automatic Restore
Data type: REG_DWORD
Radix: Hexadecimal
Value data: 1 (Default 0)
5. Quit Registry Editor.
6. Restart FRS.
If these steps do not modify the default settings and the automatic
re-initialization is not turned on, you need to manually re-initialize the
replica tree. At a convenient time, make the following changes to the
registry:
1. Stop FRS.
2. Start Registry Editor (Regedt32.exe).
3. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup
/Restore/Process
at Startup
4. On the Edit menu, click Add Value, and then add the following registry
value:
Value name: BurFlags
Data type: REG_DWORD
Radix: Hexadecimal
Value data: D2
5. Quit Registry Editor.
6. Restart FRS.
MORE INFORMATION
================
For additional information about SP3 updates to the File Replication
service,
click the article number below to view the article in the Microsoft
Knowledge
Base:
Q307319 File Replication Service Improvements in Windows 2000 SP3
--
--Brian Desmond
Windows Server MVP
desmondb@payton.cps.k12.il.us
Http://www.briandesmond.com
Taken from http://www.pcreview.co.uk/forums/thread-1446618.php
Monday, April 5, 2010
How to enbable SMTP Authentication on Konica Minolta Bizhubs
Many email servers will not allow anonymous or non-verified users to send email. They require the sender to be a verified, authorized user. Therefore these email servers need the user to enter a valid SMTP User Name and Password.
On both the Konica Minolta di2010-3510 and bizhub 200-350 series SMTP authorization is not a default choice to enter. However, you can change soft-switch 380 to allow SMTP Authentication.
For step by step how to turn this on both the bizhub 200-350 series AND di2010-3510 series:
At Copier -
Utility/Counter > Admin Management > Enter admin PW (12345678 - default for 200-350's, 00000000 default for 2010-3510's) > Enter > Admin. 2 > Software SW > Mode Selection > 380 > Hex Selection > enter 44 > Enter
Now you can go and set the SMTP authentication info
Network Settings > SMTP Settings > SMTP Server Address > Enter appropriate SMTP IP Address > Port > (Default is 25 - for most applications leave at 25) > Email Address Enter appropriate Email Return Address > Enter > SMTP User Name > enter appropriate SMTP account User Name > SMTP Authentication Password > Enter appropriate SMTP account password > Enter
From http://www.copytechnet.com/forums/konica-minolta/7220-bizhub-250-a.html
On both the Konica Minolta di2010-3510 and bizhub 200-350 series SMTP authorization is not a default choice to enter. However, you can change soft-switch 380 to allow SMTP Authentication.
For step by step how to turn this on both the bizhub 200-350 series AND di2010-3510 series:
At Copier -
Utility/Counter > Admin Management > Enter admin PW (12345678 - default for 200-350's, 00000000 default for 2010-3510's) > Enter > Admin. 2 > Software SW > Mode Selection > 380 > Hex Selection > enter 44 > Enter
Now you can go and set the SMTP authentication info
Network Settings > SMTP Settings > SMTP Server Address > Enter appropriate SMTP IP Address > Port > (Default is 25 - for most applications leave at 25) > Email Address Enter appropriate Email Return Address > Enter > SMTP User Name > enter appropriate SMTP account User Name > SMTP Authentication Password > Enter appropriate SMTP account password > Enter
From http://www.copytechnet.com/forums/konica-minolta/7220-bizhub-250-a.html
Subscribe to:
Posts (Atom)