G
grfabio
Hello all,
first, I will explain my current situation: I have my image running
from a CD ROM, via RAM DISK, so I dont use EWF. To keep
data saved, as I can't write to CDROM, I have another IDE disk (DOM
32M), with
FAT FORMAT. I have lots of supplies of these DOM's, and everytime that
I have a new brand or a new model of DOM I need to recreate all my
CDs, because, in other way the DOM will not be recognized. So to
recognize it I have to run my pos FBA image from an hard disk, put the
DOM to be recognized, and after that, write the CD. My question is: is
there any way to make my image recognize any DOM, as it is a Storage
Disk ? Is there any component that I'm missing ?
Just as information: I don't need to install any drivers to use this
DOM. I just have to put it in motherboard and run my image from a hard
disk. The only difference that I noticed is that every new brand /
model of DOM put itself in the HKEY_LOCAL_MACHINE\SYSTEM
\CurrentControlSet\Enum\IDE. It was not a problem for me up to now,
but now I got a DOM model that put a different key name for each
hardware, because it considers the DOM's "serial number" as a
differente piece of hardware.
Any ideas ??
Thanks in advance,
Fabio Gianzanti
first, I will explain my current situation: I have my image running
from a CD ROM, via RAM DISK, so I dont use EWF. To keep
data saved, as I can't write to CDROM, I have another IDE disk (DOM
32M), with
FAT FORMAT. I have lots of supplies of these DOM's, and everytime that
I have a new brand or a new model of DOM I need to recreate all my
CDs, because, in other way the DOM will not be recognized. So to
recognize it I have to run my pos FBA image from an hard disk, put the
DOM to be recognized, and after that, write the CD. My question is: is
there any way to make my image recognize any DOM, as it is a Storage
Disk ? Is there any component that I'm missing ?
Just as information: I don't need to install any drivers to use this
DOM. I just have to put it in motherboard and run my image from a hard
disk. The only difference that I noticed is that every new brand /
model of DOM put itself in the HKEY_LOCAL_MACHINE\SYSTEM
\CurrentControlSet\Enum\IDE. It was not a problem for me up to now,
but now I got a DOM model that put a different key name for each
hardware, because it considers the DOM's "serial number" as a
differente piece of hardware.
Any ideas ??
Thanks in advance,
Fabio Gianzanti