> I have read many posts and tried many things but can't get VPC to
> recognize my CD. I have tried both Primary and the default, Secondary.
> It will open the try with either setting but but won't read anything. I
> also tried creating and loading an ISO image with no luck. I was able
> to install an OS because it was MS-DOS and I used floppies. After
> selecting "Use Physical Drive D" or "Capture ISO Image" I am attempting
> to switch to the D drive from the command prompt so I can run setup exe
> on the CD. I am simply typing "D:" and the C prompt but get the old
> "Invalid Drive Specification" message. What am I missing here?
>
> Thanks,
> John

>Well ..... I added the DOS addtiions and when I boot I now see the
>startup file, auotexec.bat and config.sys loading mouse drivers and
>MSCDEX. THe parameters for MSCDEX tell me my CD should be the D drive
>but I still get nothing. However, I do have an E drive. In it is a
>folder named "system". In there is a folder named "drivers". and in
>there is a bunch of folders. One named "APP_0001". It happens to
>contain files from a folder on my Host C drive. What is happening here?
>
>Thanks again,
>John
>

> Well ..... I added the DOS addtiions and when I boot I now see the
> startup file, auotexec.bat and config.sys loading mouse drivers and
> MSCDEX. THe parameters for MSCDEX tell me my CD should be the D drive
> but I still get nothing. However, I do have an E drive. In it is a
> folder named "system". In there is a folder named "drivers". and in
> there is a bunch of folders. One named "APP_0001". It happens to
> contain files from a folder on my Host C drive. What is happening here?
>
> Thanks again,
> John
>
> (email address - cut out) wrote:
>> I have read many posts and tried many things but can't get VPC to
>> recognize my CD. I have tried both Primary and the default, Secondary.
>> It will open the try with either setting but but won't read anything. I
>> also tried creating and loading an ISO image with no luck. I was able
>> to install an OS because it was MS-DOS and I used floppies. After
>> selecting "Use Physical Drive D" or "Capture ISO Image" I am attempting
>> to switch to the D drive from the command prompt so I can run setup exe
>> on the CD. I am simply typing "D:" and the C prompt but get the old
>> "Invalid Drive Specification" message. What am I missing here?
>>
>> Thanks,
>> John
>

> When the old installers start the setup process they put the tools in a ram
> drive called D: and E: is used for the cd drive. After installation the cd
> drive will become the D: drive. I don't know if that is what you are seeing
> but might be what is going on.
>
> <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Well ..... I added the DOS addtiions and when I boot I now see the
> > startup file, auotexec.bat and config.sys loading mouse drivers and
> > MSCDEX. THe parameters for MSCDEX tell me my CD should be the D drive
> > but I still get nothing. However, I do have an E drive. In it is a
> > folder named "system". In there is a folder named "drivers". and in
> > there is a bunch of folders. One named "APP_0001". It happens to
> > contain files from a folder on my Host C drive. What is happening here?
> >
> > Thanks again,
> > John
> >
> > (email address - cut out) wrote:
> >> I have read many posts and tried many things but can't get VPC to
> >> recognize my CD. I have tried both Primary and the default, Secondary.
> >> It will open the try with either setting but but won't read anything. I
> >> also tried creating and loading an ISO image with no luck. I was able
> >> to install an OS because it was MS-DOS and I used floppies. After
> >> selecting "Use Physical Drive D" or "Capture ISO Image" I am attempting
> >> to switch to the D drive from the command prompt so I can run setup exe
> >> on the CD. I am simply typing "D:" and the C prompt but get the old
> >> "Invalid Drive Specification" message. What am I missing here?
> >>
> >> Thanks,
> >> John
> >

> Well, I seem to have gotten it. THe CD I was using was previously used
> for something else and what I was seening was files from the old burn,
> even though the were removed they must have still been in the TOC or
> something like that. ANyways, I am trying to install and run an old DOS
> game called Descent. I have it installed and configured but when it
> launches I get an error, "An internal virtual machine error (3) has
> occurred.". It is trying to load DOS/4GW. Any ideas?
>
> Thanks,
> John
>
>
> Colin Barnhorst (remove) wrote:
>> When the old installers start the setup process they put the tools in a
>> ram
>> drive called D: and E: is used for the cd drive. After installation the
>> cd
>> drive will become the D: drive. I don't know if that is what you are
>> seeing
>> but might be what is going on.
>>
>> <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Well ..... I added the DOS addtiions and when I boot I now see the
>> > startup file, auotexec.bat and config.sys loading mouse drivers and
>> > MSCDEX. THe parameters for MSCDEX tell me my CD should be the D drive
>> > but I still get nothing. However, I do have an E drive. In it is a
>> > folder named "system". In there is a folder named "drivers". and in
>> > there is a bunch of folders. One named "APP_0001". It happens to
>> > contain files from a folder on my Host C drive. What is happening here?
>> >
>> > Thanks again,
>> > John
>> >
>> > (email address - cut out) wrote:
>> >> I have read many posts and tried many things but can't get VPC to
>> >> recognize my CD. I have tried both Primary and the default, Secondary.
>> >> It will open the try with either setting but but won't read anything.
>> >> I
>> >> also tried creating and loading an ISO image with no luck. I was able
>> >> to install an OS because it was MS-DOS and I used floppies. After
>> >> selecting "Use Physical Drive D" or "Capture ISO Image" I am
>> >> attempting
>> >> to switch to the D drive from the command prompt so I can run setup
>> >> exe
>> >> on the CD. I am simply typing "D:" and the C prompt but get the old
>> >> "Invalid Drive Specification" message. What am I missing here?
>> >>
>> >> Thanks,
>> >> John
>> >
>