raijinzrael: kazblox has apparently ran into a ATAPI/IDE handling bug that intentionally prevents some accurate CD checks from passing, causing certain software to not work regardless of what CD emulation software that you’re using.

I doubt you’ll find anything as mature as KVM, or VMware/Hyper-V… Of course there is the ulimate in insanity, pass the disks native to a 2000 VM running veritas inside of the hypervisor of your choice, and share the storage back out.

Bhyve is the hypervisor on FreeBSD, I believe it will currently run BSD and Linux guests, Windows is in the works and is half way working on the 11-CURRENT development branch. Last I checked anyway.

I have a NAS with 20TB of storage across 12 disks, with redundancy. Its pretty slick, and safer than RAID.

FreeBSD is an option, but is there a decent hypervisor on top of it? If this was only a NAS box I would run freenas or nas4free or whatever it was called. But I also run guest VMs on top of it.

That is the way I remember it, and there was some module to purchase by Veritas to have VxFS, although I can’t say I recall anyone using it, I think Exchange or SQL had some weird issues or maybe it was the overall, “it’s not NTFS, it’s not in our systems” feeling.

Compared to the primitive volume management of NT 3.1/3.5/3.51/4.0 veritas was a welcome change!

I must apologise that I posted all over the place in the first place. The info that I posted is in the PCem General forum.

I’m gonna have to stick with OS/2 2.0 and limit the size of the drive to no larger than 500 MB.

I didn’t know that IMDisk will never produce proper virtual CD-ROMs, disk drivers or floppy disks. I might have to find a freeware utility that will emulate virtual CD-ROMs for sure.

IMDisk doesn’t produce proper virtual cdroms, nor, disks drivers or floppy drives, at least in the way that things like Daemon Tools/Alcohol/VFD/Firadisk/WinVBlock do. Imdisk drives just emulate enough of a drive so explorer shell and programs which access the drive via standard win32 openfile calls can see and play with them. But will not be enough for any program who tries to access the drives directly, as them aren’t complete ATAPI/SCSI devices. That’s why Pcem fails.

You need a program which emulates drives way better so PCEm can access them.

what slirp crashed the cd-rom?! I need more info. Also you can post these in the pcem post from last time, I see everything.

Uh, Neozeed. Have you tested OS/2 Warp 3 floppy and CD-ROM installation in PCem?

So far, I get a format error when trying to install Warp 3 from floppies and Tom told me that your SLiRP networking code caused the CD-ROM installation of OS/2 Warp 3 to crash PCem! The CD-ROMs that I used were from a mounted Warp 3 ISO mounted as drive N via IMDisk.