E:\UBCD4Win.350>"E:\UBCD4Win.350\vdk" open 0 "E:\UBCD4Win.350\iso_root\kicker.im g" /RW /L:Z: Virtual Disk Driver for Windows version 3.1 http://chitchat.at.infoseek.co.jp/vmware/ Installed the Virtual Disk Driver. Started the Virtual Disk Driver. Failed to decide type of 'E:\UBCD4Win.350\iso_root\kicker.img'. Open as a simple sector image file. Virtual Disk 0 Failed to open the virtual disk image. The data is invalid. E:\UBCD4Win.350>"E:\UBCD4Win.350\vdk" link 0 1 Z: Virtual Disk Driver for Windows version 3.1 http://chitchat.at.infoseek.co.jp/vmware/ Failed to assign the drive letter 'Z' to disk 0 partition 1. The system cannot find the file specified. ... E:\UBCD4Win.350>vdk driver Virtual Disk Driver for Windows version 3.1 http://chitchat.at.infoseek.co.jp/vmware/ Driver File : E:\UBCD4Win.350\vdk.sys Driver Version : 3.1 Start Type : DEMAND Driver Status : RUNNING ***** Number of Disks : 4
As you can see, for me, the vdk driver is able to load. It just doesn't seem to like the kicker.img file for some reason. I temporarily uninstalled all security software and tried it in safe mode, too, no luck. I'm running it in a VirtualBox environment with XP SP3 32-bit as both host and guest. I'd attach the kicker.img file as a 48k zip file to this post if I knew how. Maybe I can upload it to a website if you want to look at it. Any help with this would be appreciated.