• site home
  • blog home
  • galleries
  • contact
  • underwater
  • the bleeding edge

the last word

Photography meets digital computer technology. Photography wins -- most of the time.

You are here: Home / The Bleeding Edge / Virtualization

Virtualization

April 8, 2011 JimK 7 Comments

For a dozen years, I’ve owned an Imacon Flextight scanner. It started life as a Precision II, and I bought the Imacon kit that supposedly upgraded it to a Precision III. The kit consisted of a firmware upgrade, a third-party FireWire to SCSI converter, and a stick-on rubber thingy with a “III” on it to go over the “II” on the scanner. Since I’d paid a couple of thousand bucks for the upgrade, I wasn’t very happy. It seemed like the only thing of value was the firmware upgrade.

Years later, I realized what a truly lousy deal it was. Imacon stopped supporting the SCSI-based scanners in their new software. But I was covered, right? Nope. They still supported real Flextight Precision III’s, but not Precision II’s that had been made into Precision III’s through their upgrade process. They froze the driver for my scanner at a version that ran on Windows XP, but on no newer operating system.

I didn’t want to dedicate a computer running XP to the scanner. My first thinking was to make the boot disk removable, and boot to Vista with one disk and XP with another. Technically, it worked fine, but it gave the Vista copy protection software fits. Every time I would put Vista back in the boot drive location and fire up the machine, I’d get complaints that were only resolvable with a phone call to Microsoft.

The phone calls got real old, so I then installed a boot manager from Acronis. It worked fairly well, but had two annoying problems. First, the support for my mouse was buggy. Second, every so often Windows would wipe it out and I’d have to reinstall it.

I thought about virtualization, but it seemed like too much trouble, and I was worried about finger-pointing if I had a problem running Windows on virtualization software from another vendor.

In the 80s and 90s, when I was working for IBM, I was a user of virtualization software that ran on IBM mainframes. It was called, VM, which stood for virtual machine. Some of IBM’s product names are amazingly generic: there was a popular programming language called APL, which stood for, you guessed it, a programming language. VM is now more than 40 years old, and I hear it’s still going strong.

In the last five or six years, virtualization has enjoyed a renaissance in the server and personal computer worlds. Mac users employ virtualization to run Windows on their Intel-based machines. Systems administrators run virtual machines on servers to allow optimization of the OS environment for various applications, to allow testing to take place in convenient and safe environments, and to improve hardware utilization, thereby saving money and energy. Developers use it to conveniently test software under many different operating systems and configurations. End users and IT people use it to set up safe environments for testing applications and new operating systems.

Microsoft has leapt into the virtualization business with a number of products. Most of them are aimed at servers and large businesses, but one is an easy to use, free implementation that allows Windows XP to run on a Microsoft virtual machine on a Windows 7 computer. To get it, go to http://www.microsoft.com/windows/virtual-pc/download.aspx.  You’ll need to download and install the virtual machine hypervisor and the Windows XP OS separately. IF you’re running a version of Win 7 before SP1, you’ll need to run an update at the end of the installation

When you run the installation programs, you’ll be treated to what looks like a conventional XP install in a window of your Win 7 desktop, complete with “restarts” that cause the virtual machine to be shut down and restarted, but you won’t see the BIOS, because it’s just a virtual restart. Then you’ll have to install a bunch of updates on your virtual XP installation, and watch a bunch more fake restarts. Finally, you’ll need to load antivirus software on your XP installation, since your Win 7 AV won’t offer any protection.

The version of XP provided by Microsoft is SP 3, which hasn’t got the patch to correct the time for the current law. Here’s a screen shot of the lower right corner of a window of a virtual machine running XP with the lower right corner of the Win 7 host in the bottom right of the image. Note the one-hour difference in the time.

time wrong

All in all, this is an effective way to run what are quaintly known as “legacy apps”, even if under the covers there’s lot happening.  This is no halfway measure, you’re not running something that’s compatible with XP, you’re running XP, warts and all, and the initial SP 3 version takes 50 or 60 updates to get it up to the current state of the XP OS. I like that. It indicates a seriousness on the part of the folks at Redmond in giving the user fine-grain control over anything that might mess with program compatibility – you can back out any update that screws it up.

I haven’t yet installed the SCSI card to drive the Imacon scanner, but I have installed Chromix ColorThink, which doesn’t run right under Win 7. It works fine under virtual XP.

The Bleeding Edge

← Win 7 Aero & 30 bit color Tech hall of shame: NYT digital delivery →

Comments

  1. Alex says

    February 14, 2012 at 5:12 pm

    Hey Jim, thanks for the post. I just bought an Imacon Precision II scanner, and am wondering if you’ve any update if you’ve gotten it to work with Windows 7 Professional (in XP virtualization)? If so I’d love to know, as I’m either going to pull the trigger on a dedicated p.c. with old xp install, or new one with virtual (buying a power mac g4 for is out, as it’d be just too slow and bound to die soon). For the SCSI connection I’d be looking to get an Adaptec 29320LPE ASC-29320LPE Single Channel Ultra 320 SCSI Controller.

    Reply
    • Jim says

      February 14, 2012 at 5:35 pm

      I never did get it to work under Win 7. I’d go with a real XP installation.

      Sorry,

      Jim

      Reply
  2. Alex says

    February 15, 2012 at 6:07 am

    Ok, thanks!

    Reply
  3. m21gunner says

    April 20, 2012 at 12:11 pm

    How much is the Imacon Flextight scanner?

    Reply
    • Jim says

      April 20, 2012 at 1:30 pm

      The one I have cost about $18K new in 1998. The current Imacon Flextight X1 scanner sells for about $17K new today.

      Jim

      Reply
  4. HanJun says

    July 19, 2014 at 10:06 am

    HI,Precision II upgraded it to a Precision III firmware. Could you send a copy to me.Thanks

    Reply
    • Jim says

      July 20, 2014 at 5:08 pm

      I’m not sure I understand the question. If you’re looking for the firmware, you’ll have to get it from Hasselblad. Back in the day they charged a couple of thousand bucks, as I remember, but who knows what they charge now…

      Jim

      Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

May 2025
S M T W T F S
 123
45678910
11121314151617
18192021222324
25262728293031
« Apr    

Articles

  • About
    • Patents and papers about color
    • Who am I?
  • How to…
    • Backing up photographic images
    • How to change email providers
    • How to shoot slanted edge images for me
  • Lens screening testing
    • Equipment and Software
    • Examples
      • Bad and OK 200-600 at 600
      • Excellent 180-400 zoom
      • Fair 14-30mm zoom
      • Good 100-200 mm MF zoom
      • Good 100-400 zoom
      • Good 100mm lens on P1 P45+
      • Good 120mm MF lens
      • Good 18mm FF lens
      • Good 24-105 mm FF lens
      • Good 24-70 FF zoom
      • Good 35 mm FF lens
      • Good 35-70 MF lens
      • Good 60 mm lens on IQ3-100
      • Good 63 mm MF lens
      • Good 65 mm FF lens
      • Good 85 mm FF lens
      • Good and bad 25mm FF lenses
      • Good zoom at 24 mm
      • Marginal 18mm lens
      • Marginal 35mm FF lens
      • Mildly problematic 55 mm FF lens
      • OK 16-35mm zoom
      • OK 60mm lens on P1 P45+
      • OK Sony 600mm f/4
      • Pretty good 16-35 FF zoom
      • Pretty good 90mm FF lens
      • Problematic 400 mm FF lens
      • Tilted 20 mm f/1.8 FF lens
      • Tilted 30 mm MF lens
      • Tilted 50 mm FF lens
      • Two 15mm FF lenses
    • Found a problem – now what?
    • Goals for this test
    • Minimum target distances
      • MFT
      • APS-C
      • Full frame
      • Small medium format
    • Printable Siemens Star targets
    • Target size on sensor
      • MFT
      • APS-C
      • Full frame
      • Small medium format
    • Test instructions — postproduction
    • Test instructions — reading the images
    • Test instructions – capture
    • Theory of the test
    • What’s wrong with conventional lens screening?
  • Previsualization heresy
  • Privacy Policy
  • Recommended photographic web sites
  • Using in-camera histograms for ETTR
    • Acknowledgments
    • Why ETTR?
    • Normal in-camera histograms
    • Image processing for in-camera histograms
    • Making the in-camera histogram closely represent the raw histogram
    • Shortcuts to UniWB
    • Preparing for monitor-based UniWB
    • A one-step UniWB procedure
    • The math behind the one-step method
    • Iteration using Newton’s Method

Category List

Recent Comments

  • JimK on Goldilocks and the three flashes
  • DC Wedding Photographer on Goldilocks and the three flashes
  • Wedding Photographer in DC on The 16-Bit Fallacy: Why More Isn’t Always Better in Medium Format Cameras
  • JimK on Fujifilm GFX 100S II precision
  • Renjie Zhu on Fujifilm GFX 100S II precision
  • JimK on Fuji 20-35/4 landscape field curvature at 23mm vs 23/4 GF
  • Ivo de Man on Fuji 20-35/4 landscape field curvature at 23mm vs 23/4 GF
  • JimK on Fuji 20-35/4 landscape field curvature at 23mm vs 23/4 GF
  • JimK on Fuji 20-35/4 landscape field curvature at 23mm vs 23/4 GF
  • Ivo de Man on Fuji 20-35/4 landscape field curvature at 23mm vs 23/4 GF

Archives

Copyright © 2025 · Daily Dish Pro On Genesis Framework · WordPress · Log in

Unless otherwise noted, all images copyright Jim Kasson.