SP112 Laser Printer Parts / Disassembly / Break-down

I found a cheap Ricoh Mono Laser Printer – SP112, (Thanks OzBargain! https://www.ozbargain.com.au/node/238682) and wanted to see if I could source some cheap stepper motors. Long story short – there are no stepper motors in this printer. There are however many parts that could be useful. See below for photos. Let me know if you know what they are / are for.

Not Sure

Laser Sensor?

Laser Sensor?

Laser Sensor?





Power Supply

Power Supply

Not Sure / Sensor?


Not Sure

Heating Element

The one Motor

More Gears

Power Cable Socket

Top Buttons / Status Lights

More Gears


SMC Pentax-DA* 50-135mm F2.8 ED [IF] SDM Fix / Repair / Workaround

Just like many other Pentax-DA* 50-135mm users out there, I have the SDM issue where the lens will no longer auto focus. While possible to repair yourself (not recommended) I have found a simple work-around that seems to get the lens working. If you listen carefully (ear to the lens body) when you depress the shutter you will hear a high-pitch sound. If you keep pressing the shutter (triggering the auto focus), you may notice the pitch getting higher and higher. I have found after about 15 times, the lens will start to auto focus again. Depending on how much you then use the lens your mileage will vary.

Need to work out the IP address and MAC addresses of your Hyper-V VMs in SCVMM?

If you have been trying to get information out of VMM using the ‘traditional’ Get-VM commandlet you may have noticed it throws an error similar to this:

get-vm : The cmdlet cannot find a specified class. Verify that the relevant feature is enabled on the operating system.

Now this threw me off as being an incorrect command. What I found is that you need to specify the VMM server name.

If you just want a list of all the VMs, you can run the following:

I also noticed that if you run get-vm by itself in the PowerShell (don’t forget to run Import-Module -Name “virtualmachinemanager”) it does not need the -VMMServer to be specified.

Anyhoo – once you have the command to spit out all the VMs in your environment, its a simple pipe to select the information you need:

Your output should look something like this:

VMMVMsIPSimple as that!

Change Default Windows Audio Device via Command Line

I just had to share this!

I use 3 different audio devices (Speakers, Stereo Headset and a 7.1 Headset) for various different applications. While Windows is now relatively smart about how it sets the default device when detected, it still requires removing / adding the device.

I thought to myself, wouldn’t it be great if I could just create a script that I could execute before running certain applications that would allow me to set the audio device automatically. Most search results provided links to third party macro / hotkey applications which was not what I was looking for. Looking deeper I came across a gem of an application, AudioEndPointController by Dan Stevens.

This application lets you list the audio output devices attached to the computer and can also set the default output. Using shortcuts to call the executable, I can parse the audio device number of my choosing, and the default device flips, simple as that. Chrome plays well and any audio playing (Youtube etc) will immediately switch over. Firefox (for me) requires a restart.

I Googled for images of my headphones / speakers and converted them to .ico files so I could have graphical shortcuts on the start bar. I used http://www.convertico.com/ to convert them online. Works great!

Compulsory – yet tiny image:


Hyper-V Getting MAC Address using VM Name

As part of my automated provisioning (yes – System Center and Sysprep will probably be a better option, but hey whatever) script, I need to be able to automatically assign an IP address to a VM. At this point, the only way I can see this being a possibility is to mount the VHD before booting then copying a script that will set the correct IP address to an autostart location.

The ‘script’ is broken down into two parts. The first needs to run on the node, and create the second script inside the VHD. The second script then needs to identify what network adapter/s are present and assign the correct IP address to each.

The first challenge is finding out how to have the second script identify the correct adapter. I initially though about testing connectivity after the IP address was set, and upon a failure, revert the changes and try the next adapter present. Rather than doing this, I found you can get the MAC address for a VM from the Hyper-V node, and filter based on which Virtual Switch the interface is attached to:

The following example will get the MAC address for a VM based on the VM name, and the network it is attached to:

This returns a MAC address.

I believe I can then use this MAC address in the second part of the script to pull the network adapter name.

Something along the lines of this:

Once I have the correct adapter name, I can use this in an IP address setting script to set the correct IP / gateway etc essentially automating the networking side of provisioning.

At this point there are a few things I have yet to confirm that might make the above attempt futile. First, I do not know if I can run a powershell script on startup – I know there are issues with signed code etc, and this might mean a freshly provisioned system will not allow unsigned code to run – especially if it needs administrator permissions. Second – I don’t know how this will work with a sysprepped image. It is possible (probable?) that with a sysprep image, the network configuration information could be copied to the sysprep config eliminating the need for an autorun script.

You can see an example of a powershell script to assign IP addresses here: https://social.technet.microsoft.com/Forums/en-US/winserverpowershell/thread/040b8993-d737-4436-8fb1-29187583e7d1/

Copy to mounted VHD with PowerShell for automated Hyper-V Provisioning – Part II

While I initially tried to get the Powershell Mount-VHD cmdlet working – I gave up as it didn’t seem to exist (despite obvious documentation: https://technet.microsoft.com/en-us/library/hh848551.aspx)

I was using a Server 2012 DS for testing purposes, but as I was just working on the drive letter side of things – I had yet to install the Hyper-V role. Turns out that Mount-VHD is exactly what I need to get the driveletter of a VHD and requires Hyper-V to be installed. The last example on the Microsoft Site gives you all you need to know:

With a little modification we can ensure that the System Reserved partition does not get in the way:

This is what you will get after mounting using the above command:


You can then select the driveletter column to get what you need:

Much more simple than my previous attempt!


© 2016 Chris's Blog

Theme by Anders NorénUp ↑