# Thursday, 17 May 2007

Can't install Service Pack (or some/all other updates) directly, from Windows Update or by WSUS.  See http://support.microsoft.com/default.aspx?scid=kb;en-us;822798 for solutions.

This worked for me:

create batch file (catroot2.cmd)

net stop cryptsvc
ren %systemroot%\System32\Catroot2 oldcatroot2
net start cryptsvc
cd %systemroot%\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
del /Q tmp*.cat

Then delete all tmp*.cat files from %systemroot%\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} (or add to batch file, as above)

win | 2003 | sbs | xp | wsus
Thursday, 17 May 2007 15:32:34 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Tuesday, 24 April 2007



Jumper Settings:



Jumper Setting for EPP Printer Card LPT 1.2&3

. 27B 37B 3BC
JP 5 1-2 1-2 2-3

1-2 2-3
JP 4 IRQ 7 IRQ 5


1-2 2-3

Tuesday, 24 April 2007 18:25:25 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Thursday, 08 March 2007

EventID:   1
Source:   VDS Basic Provider 1.0
Data:      Unexpected failure. Error code: 45D@01020004

[Windows Mail] could not be started. The application was unable to create teh spooler object. Your computer may be out of memory or your disk is full. (0x80040155)

EventID:   1
Source:      VDS Basic Provider 1.0
Data:         Failed to open device [\path\to\harddisk\Partitionx]. Error code: 2@01050001

The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043c from line 45 of d:\vistartm\com\complus\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.


Thursday, 08 March 2007 19:54:58 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Wednesday, 14 February 2007

Just some notes:


I order to run  an IPSEC/NAT-T type VPN you need to insert the following registry keys on the client :






Now... I'm not quite sure that these alone will help you get connected.
Make sure that since you are connecting from a non-domain member that you certificate is properly installed.

Import the Administrator-Cert to both
Local Machine: "Personal" & "Trusted Root Certification Authorities"

This in combination with the above registry-hack should do it.

BTW: The one for SP 2 is documented in:

The one for Vista is not... but it works  

[TX Geir Johansen, isaserver.org]

OK, here is a way to do it (but it is not an easy

1) You need to use certmgr.msc on the Vista Client
2) You need to generate Custom Request in the console
(see Create a Custom Certificate Request in the Help
3) Best to add Custom subject information (be sure to
include an Alternate Name that includes the User
Principal Name
4) Save the file to a PKCS#10 request

Create a custom v2 certificate template that allows the
Subject to be created in the Request. Base it on the
template you want to use (for the love of G*D, do not
use User <G>) Ensure that the template is available at
the CA you are using. Assume it is named VistaUser

You now use the Certsrv Web page to submit the request
1) Connect to https://CAName/certsrv
2) Provide credentials from the domain
3) Choose Request a Certificate
4) CHoose Advanced Certificate Request
5) Choose Submit a certificate request by using a base-  
64-encoded CMC or PKCS #10 file, or submit a renewal
request by using a base-64-encoded PKCS #7 file.
6) Paste the contents of the file created in the first
procedure into the Saved Request box
7) Choose the VistaUser template in the Certificate
Template sectino
8) Click Submit
9) Save the issued certificate to a PKCS#7 file (all
certs in the chain)

Go back to the Vista box
1) Import the PKCS#7 file
2) Put all certs in the Personal store (for now)
3) Once the import is complete, move the CA certificates
into the appropriate stores (root in the root, all other
CAs in the intermediate store
4) Use the certificate

P.S. Please do not ask for more detailed steps <G>

In article <D85CB163-D832-4D40-B009-B5A28A685BF0
@microsoft.com>, S...@discussions.microsoft.com says...


vista | vpn | 2003
Wednesday, 14 February 2007 20:26:40 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Saturday, 10 February 2007

IE7 installs newer version of psapi.dll.  Stop all Exchange services and remove/rename psapi.dll in \Exchsrvr\bin\. Restart Exchange services.

Saturday, 10 February 2007 11:01:09 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback

Win95 doesn't like hardware virtualisation being enabled in a virtual machine; crashing on load with a

While initializing device IOS:
Windows protection error.  You need to restart your computer.

Seems the Core2Duo 2.66 is too fast for Win95 (4.00.950 b).  The following Compaq KB article was reproduced by Glen Ventura:

Errors May Occur When Installing Windows 95 on PCs with Pentium III or
Pentium 4 Processor

NOTICE: The information in this document, including products and software
versions, is current as of the Release Date below. This document is subject
to change without notice.

RELEASE DATE: October 2001

The following errors may occur when installing Microsoft Windows 95 (OSR1 or
OSR2) on a computer configured with an Intel Pentium III processor (1-GHz or
faster) or any Intel Pentium 4 processor:

Device IOS failed to initialize. Windows Protection Error. You must reboot
your computer.
Windows Protection Error. You must reboot your computer.
While initializing device IOS: Windows protection error.

This issue is not specific to Compaq products. It may occur on any computer
configured with an Intel Pentium III (1 GHz or faster) or any size Intel
Pentium 4 processor and Microsoft Windows 95 (OSR1 or OSR2).

This issue has been documented in Microsoft Knowledge Base Article Q192841
for AMD K6-2 processors but also applies to the Intel Pentium III (1-GHz or
faster) and Pentium 4 processors. Most users can follow the procedures
outlined in the Microsoft Knowledgebase article below (see Option 1 ) to
resolve the issue. However, there are instances in which Windows 95 systems
cannot be started in Safe Mode (required for the Knowledgebase article
procedures). In those instances, users can manually apply the patch using
the procedure outlined in Option 2, below.

Option 1: Useable if the system can be started in Safe Mode


The AMD-K6-2 update has been revised to incorporate a newer version of
Vfbackup.vxd file. For information about this update, please see the
following article in the Microsoft Knowledge Base:

Q234259 Revision To AMD K6-2/350 Central Processing Unit Update
A supported fix that corrects this problem for Microsoft Windows 95 OEM
Service Release versions 2, 2.1, and 2.5 is now available from Microsoft,
but has not been fully regression tested and should be applied only to
computers experiencing this specific problem. If you are not severely
affected by this specific problem, Microsoft recommends that you use the
next release of Windows.

To resolve this problem immediately, visit the following Microsoft Web site:


Scroll down to the Service Packs section and then click the link to download
the Windows 95 Update for AMD-K6-2/350.

NOTE: This fix does not correct the problem for the retail version of
Windows 95. In addition, versions of the Amdk6upd.exe update dated "09/18/98
11:00am" do not replace the Ntkern.vxd file in OSR 2.1 and OSR 2.5. To
determine the version of the Ntkern.vxd file installed on your computer,
right-click the Ntkern.vxd file in the Windows\System\Vmm32 folder, click
Properties, and then click the Version tab. If the version number is not
4.03.1213, you should obtain and install a new version of the update, as
described below. Note that the version of the original Ntkern.vxd file is

To install this update, follow these steps:

Download the Amdk6upd.exe file to a floppy disk. Download the file from
another computer, if necessary.

Restart your computer. When you see the "Starting Windows 95" message, press
the F8 key, and then choose Safe Mode from the Startup menu.

If your computer starts in Safe mode, skip to step 6. If you cannot start
Windows, continue with step 4.

Restart your computer. When you see the "Starting Windows 95" message, press
the F8 key, and then choose Command Prompt Only from the Startup menu.

At the c:\ prompt, type win /d:m to start Windows in Safe mode.

Insert the floppy disk containing the Amdk6upd.exe file you downloaded in
step 1, and then use Windows Explorer or My Computer to double-click the

Follow the instructions on the screen to install the update.

The following file is available for download from the Microsoft Download

Download Amdk6upd.exe now
For additional information about how to download Microsoft Support files,
click the article number below to view the article in the Microsoft
Knowledge Base:

Q119591 How to Obtain Microsoft Support Files from Online Services
Microsoft used the most current virus detection software available on the
date of posting to scan this file for viruses. Once posted, the file is
housed on secure servers that prevent any unauthorized changes to the file.

Microsoft has confirmed this to be a problem in Microsoft Windows 95 and OEM
Service Release versions 2, 2.1, and 2.5.

This issue is resolved in Microsoft Windows 98.

Last Reviewed: January 29, 2001
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.

Option 2: For Windows 95 systems that cannot be started in Safe Mode.

Browse to the Microsoft Windows Update site
(http://www.microsoft.com/windows95/downloads) and download "Windows 95
Update for AMD-K6-2/350" (file name: AMDK6upd.exe ).

Extract the files from AMDK6upd.exe to a bootable floppy disk by executing
'AMDK6upd.exe /T:a:\ /C'. (Note: The switches are documented by
'AMDK6upd.exe /?').

Start Windows 95 installation following the normal procedure.

When the error occurs (usually on the first boot into Windows 95), or the
computer fails to start Windows 95, boot machine using the bootable floppy
created in Step 2.

Manually copy the updated driver files on the diskette to their proper
locations as indicated below:

The Copy to This Location paths below assume that Windows 95 is being
installed in the default location (logical drive C). If installing Windows
95 on a different logical drive, modify the paths accordingly.

File Name Copy to This Location
scsiport.pdr C:\Windows\System\IOSubsys
disktsd.vxd C:\Windows\System\IOSubsys
esdi_506.pdr C:\Windows\System\IOSubsys
hsflop.pdr C:\Windows\System\IOSubsys
cdfs.vxd C:\Windows\System\IOSubsys
vfbackup.vxd C:\Windows\System\VMM32
ios.vxd C:\Windows\System\VMM32
int13.vxd C:\Windows\System\VMM32
NOTE: The following file is needed only if the version of Windows 95 is
OSR2.1 or OSR2.5:
ntkern.vxd C:\Windows\System\VMM32

Remove the floppy disk and restart the system.

If prompted, select Normal Startup of Windows 95.

Complete Windows 95 installation procedure.

After Windows 95 is fully installed and running, execute the AMDK6upd.exe
without any command switches to register the update.

OPERATING SYSTEMS AFFECTED: Microsoft Windows 95 OSR1, Microsoft Windows 95


THIRD PARTY PRODUCTS AFFECTED: Intel Pentium 4 processor

Saturday, 10 February 2007 00:33:11 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Tuesday, 06 February 2007

Microsoft has a (beta?) tool to allow ntbackup (.bkf) files created in XP/2003/2000(?) to be accessed in Vista (and Longhorn).

The download is here.

Tuesday, 06 February 2007 10:50:00 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Friday, 02 February 2007


Friday, 02 February 2007 23:29:42 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Monday, 22 January 2007

Change shortcuts to:

"wmplayer.exe /Task:NowPlaying"


"C:\Program Files\Windows Media Player\wmplayer.exe" /Task:NowPlaying /prefetch:1



vista | WMP
Monday, 22 January 2007 10:33:01 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Saturday, 20 January 2007

1. Click Start
2. Click All Programs
3. Click Accessories
4. Right Click on Command Prompt
5. Left click on Run as Administrator
6. Click the Allow button if it asks you for permission
7. Type or copy and paste this into the command prompt window:

bcdedit.exe /set {current} nx AlwaysOff

8. Hit enter and you should see the confirmation: Operation Completed Successfully
9. Reboot and DEP should be off.

Saturday, 20 January 2007 16:25:22 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback