Category Archives: Microsoft

Windows 10 Build 10122 Stuck – With Error Message

After 24 hours, VMware gives an Error Message about an “unrecoverable error: (vcpu-0)” and points to a log file (in the host OS, Windows 8.1) for explanation:

C:\Users\bob\Documents\Virtual Machines\Windows 10 x64\vmware.log

...
2015-05-25T13:37:09.197+10:00| vcpu-0| I120: CoreDump: ei->size 18300928 : len = 18300928
2015-05-25T13:37:09.197+10:00| vcpu-0| I120: Backtrace:
2015-05-25T13:37:09.338+10:00| vcpu-0| I120: backtrace[00] frame 0x06f8ee98 IP 0x7ff714e7f14e params
0 0xfe19d480 0x45086e0 0x6f84546 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x7ff714e30000 0x0001:0x0004e14e]

2015-05-25T13:37:09.338+10:00| vcpu-0| I120: backtrace[01] frame 0x06f8f7c0 IP 0x7ff714e592e0 params
0x7ff7154dd548 0x7ff7155e72d0 0x5f1 0x6f8f840 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x7ff714e30000 0x0001:0x000282e0]

2015-05-25T13:37:09.338+10:00| vcpu-0| I120: backtrace[02] frame 0x06f8f800 IP 0x7ff7151ce195 params
0x10fb300 0x10fc180 0x1 0x110011c opus_repacketizer_destroy + 0x14ac15 [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x7ff714e30000 0x0001:0x0039d195]

2015-05-25T13:37:09.385+10:00| vcpu-0| I120: backtrace[03] frame 0x06f8f900 IP 0x7ff7151ce570 params
0x4508340 0x1100100 0x81013f6b 0 opus_repacketizer_destroy + 0x14aff0 [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x7ff714e30000 0x0001:0x0039d570]

2015-05-25T13:37:09.385+10:00| vcpu-0| I120: backtrace[04] frame 0x06f8f980 IP 0x7ff71501450e params
0x7ff7158ac710 0x7ff700000000 0x6f8f9c0 0x7ff7158ac710 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x7ff714e30000 0x0001:0x001e350e]

2015-05-25T13:37:09.385+10:00| vcpu-0| I120: backtrace[05] frame 0x06f8f9b0 IP 0x7ff7153d3752 params
0x168 0x38a0000 0 0xa36313833 opus_repacketizer_destroy + 0x3501d2 [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x7ff714e30000 0x0001:0x005a2752]

2015-05-25T13:37:09.385+10:00| vcpu-0| I120: backtrace[06] frame 0x06f8fa00 IP 0x7ff71540ecfe params
0x33000000 0x168 0 0 opus_repacketizer_destroy + 0x38b77e [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x7ff714e30000 0x0001:0x005ddcfe]

2015-05-25T13:37:09.385+10:00| vcpu-0| I120: backtrace[07] frame 0x06f8fb70 IP 0x7ff7153d3a1c params
0x7ff71555acb0 0x7ff7155272fc 0x3 0x7ff715a8b810 opus_repacketizer_destroy + 0x35049c [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x7ff714e30000 0x0001:0x005a2a1c]

2015-05-25T13:37:09.385+10:00| vcpu-0| I120: backtrace[08] frame 0x06f8fbd0 IP 0x7ff714feb686 params
0x7ff714feb5c0 0 0 0 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x7ff714e30000 0x0001:0x001ba686]

2015-05-25T13:37:09.385+10:00| vcpu-0| I120: backtrace[09] frame 0x06f8fbd8 IP 0x7fffe18313d2 params
0 0 0 0x7ff714feb5c0 BaseThreadInitThunk + 0x0022 [C:\WINDOWS\system32\KERNEL32.DLL base 0x7fffe1830000 0x0001:0x000003d2]

2015-05-25T13:37:09.385+10:00| vcpu-0| I120: backtrace[10] frame 0x06f8fc08 IP 0x7fffe1985444 params
0 0 0 0 RtlUserThreadStart + 0x0034 [C:\WINDOWS\SYSTEM32\ntdll.dll base 0x7fffe1970000 0x0001:0x00014444] 2015-05-25T13:37:09.401+10:00| vcpu-0| I120: Msg_Post: Error

2015-05-25T13:37:09.401+10:00| vcpu-0| I120: [msg.log.error.unrecoverable] VMware Player unrecoverable error: (vcpu-0)
2015-05-25T13:37:09.401+10:00| vcpu-0| I120+ NOT_REACHED d:/build/ob/bora-2700073/bora/devices/ahci/ahci_user.c:1521
2015-05-25T13:37:09.401+10:00| vcpu-0| I120: [msg.panic.haveLog] A log file is available in "C:\Users\bob\Documents\Virtual Machines\Windows 10 x64\vmware.log".
2015-05-25T13:37:09.401+10:00| vcpu-0| I120: [msg.panic.requestSupport.withoutLog] You can request support.
2015-05-25T13:37:09.401+10:00| vcpu-0| I120: [msg.panic.requestSupport.vmSupport.vmx86]
2015-05-25T13:37:09.401+10:00| vcpu-0| I120+ To collect data to submit to VMware technical support, run "vm-support".
2015-05-25T13:37:09.401+10:00| vcpu-0| I120: [msg.panic.response] We will respond on the basis of your support entitlement.
2015-05-25T13:37:09.401+10:00| vcpu-0| I120: ----------------------------------------
2015-05-25T13:37:09.401+10:00| vcpu-0| I120: USBGW: Write arbitrator op:13 len:19

And good luck deciphering that lot!

 

Build 10122 Stuck - With Error Message
Build 10122 Stuck – With Error Message

Windows 10 Build 10122 Stuck – CANNOT SHUT DOWN

Somehow, this build has got stuck. I cannot bring up the Start Screen either by hitting the Windows Key, clicking the Start Button or by hitting Cntrl + Escape.

I also cannot bring up the Notifications screen to flip in and out of Tablet Mode. This usually brings back the Start Screen.

A final resort: Since I am running Windows 10 under VMware, I can click the 3-squares-icon (Send Ctrl+Alt+Del to virtual machine). This succeeded in bringing up the blue shutdown screen, but none of the options (like Shut down, Restart or even Cancel) have any effect.

********** THIS LOOKS LIKE THE END OF WINDOWS 10 **********

 

Build 10122 Unable to Close
Build 10122 Unable to Close

To add insult to injury, I can turn on Narrator and it dutifully tells me what I am doing — AND THEN THE OS DOES NOTHING !

Build 10122 - Narrator On, but still unable to Close

Build 10122 – Narrator On, but still unable to Close

The DOS CD Command (or how to send stderr to nul)

Good old DOS.

Don’t you hate getting this message: The system cannot find the path specified. What path?

It’s usually the result of a failed CD command. But what if it’s inside a batch file? Hopeless. Wouldn’t it be better instead to have a message like: Sub-Directory “hhh” not found.

It’s easy to do in a batch file. We just have to figure a way to nullify that DOS error message.

Let’s try “cd xxx > nul”. That should do it.

What? That fails?

The reason that the error message still appears is that it is not written to Standard Output (stdout), but to Standard Error (stderr). We have to send the 2nd output to nul as well. Here’s how to do it:

cd xxx > nul 2 > nul

or cd xxx > nul 2>&1

The first sends outputs 1 and 2 to nul. The second sends stderr (output 2) to the same place as stdout (output 1). Very Unix/Linux – like syntax here.

The next thing to do is to test the success of the CD command. Luckily DOS sets the errorlevel to 0 for success and 1 (or higher) for failure.

In the DOS batch file, below, we are trying to go to a subdirectory in some deep directory tree and either doing a full dir listing, or in the case of CD failure, just listing the subdirectories available (those with <DIR> on the lines):

Rem If no parameter, just exit the batch file

if “%1” == “” goto end

cd %1 > nul 2 > nul

Rem if the CD works, give the full dir command:

if not errorlevel 1 goto fulldir

Rem “if not errorlevel 1…” means if errorlevel is not 1 or higher
Rem (in other words, zero), then execute the goto command.
Rem If the CD fails, list the subdirectories we could have chosen.

echo.
echo Sub-Directory “%1” not found:-
echo.
dir | find “<DIR>” | find /v ” .” | more
goto end

:fulldir
echo.
dir
echo.

:end

All those “echo.” commands insert blank output lines for readability. And the “find” with the /v parameter means select lines which do not contain a blank followed by a dot (” .”) – in other words do not list the directories “.” or “..”.

Here’s a typical use for such a feature. I want to go to the VB6 directory containing the source of my Application Programs:

C:\>#vb asd

Sub-Directory “asd” not found:-

23/12/2006 01:00 AM <DIR> pdfflip
04/05/2006 05:33 PM <DIR> pict
24/12/2006 04:14 PM <DIR> psflip
24/06/2005 12:17 PM <DIR> stretch
26/09/2008 04:07 PM <DIR> unscr1
13/10/2008 04:06 AM <DIR> unscr2

C:\Program Files\Microsoft Visual Studio\VB98\Aprog>

In this case the misspelt subdirectory is obvious but in general, given the original DOS error message, the user would have no idea what path The system cannot find.

PS: The more command, above, allows the output to pause at page boundaries, if necessary. The initial dir command, however, does not pause when the output is piped to another command (even with the /p parameter set by default).

The OS (Windows 7) is Dead. Long Live the OS.

The Windows 7 Beta and RC1 versions have now expired. I did not want the Windows actions of 2-hourly shutdowns for a month before finally being unable to access my data.

Very nasty, Microsoft.

I have now dropped Windows 7 completely, as I’m sure others will too — refusing the extortionate $400 pricetag.

My OS of choice is now Fedora (a totally modern, free 64-bit Linux OS). It has pleasant surprises at every turn, like displaying the local weather when hovering over the time display —

Scattered Clouds

Sent means Sent

For the normal user sitting at a computer, wanting to Send a file, they normally think of Uploading it either to a website or as an attachment via email.

Not Receiving a file from the internet.

Just normal conversational usage — contrary to the Internet Status displayed, below.

No Statistics Required.

Internet Status – Sent means Downloads

After all these years, Windows (XP) Internet Status ( Control Panel | Network Connections | Internet) has Sent and Received reversed from normal usage. [ Bob: The Windows 7 equivalent does get the directions correct. ]

From the point of view of the Internet, bytes Sent are of course Downloads. It all makes sense now:

Internet Status

To test this theory, I downloaded the latest Opera 10.50 Beta (12 MB) with the result:

Sent went from 1,470,582,553 to 1,484,554,805 (13,972,252 bytes).

Received went from 83,985,137 to 84,325,547 (340,410 bytes).

It is obvious which is the 12 MB download.

KB973525 Causes Visio Viewer to Fail

The Microsoft security update KB973525, issued on Oct 13 2009, fixes some vulnerabilities in ActiveX running under Internet Explorer.

Quoting from that article: “Known Issues. None”

Unfortunately, a serious side-effect is to make Microsoft’s own Visio Viewer refuse to load Visio files. The viewer, which runs as an Add-on within IE, only produces a little square with a red cross (in Windows XP) or a failed-image icon (in Windows 2000). Both the 2003 and the 2007 versions of Visio Viewer fail.

Visio Viewer Failed
Visio Viewer Failed

Until Microsoft issues an official fix, go to Add/Remove Programs and select KB973525 for removal.

Visio Viewer is then much happier:

Visio Viewer OK
Visio Viewer OK

Windows – Internet Sharing

After some hardware shuffling, my LAN computers could not access the internet. The main XP computer with the ADSL2+ modem connected fine.

Google to the rescue – that takes me to a Knowledge Base article by Microsoft.

On the client computer
To connect to the Internet by using the shared connection, you must confirm the LAN adapter IP configuration, and then configure the client computer. To confirm the LAN adapter IP configuration, follow these steps:

  1. Log on to the client computer as Administrator or as Owner.
  2. Click Start, and then click Control Panel.
  3. Click Network and Internet Connections.
  4. Click Network Connections.
  5. Right-click Local Area Connection, and then click Properties.
  6. Click the General tab, click Internet Protocol (TCP/IP) in the This connection uses the following items list, and then click Properties.
  7. In the Internet Protocol (TCP/IP) Properties dialog box, click Obtain an IP address automatically (if it is not already selected), and then click OK. Note You can also assign a unique static IP address in the range of 192.168.0.2 to 192.168.0.254. For example, you can assign the following static IP address, subnet mask, and default gateway:

    IP Address 192.168.0.2
    Subnet mask 255.255.255.0
    Default gateway 192.168.0.1

  8. In the Local Area Connection Properties dialog box, click OK.
  9. Quit Control Panel.

Unfortunately, they don’t say anything about setting the DNS server address, which makes all the difference:

TCP properties
TCP properties