You're right, I get exactly the same result if I rem out that line.

I then arrive at this as the most economical working configuration:

=======================
REM (some commands)

SHSUCDX /QQ /D3

REM (some commands)

DEVLOAD /Q /H C:\FDOS\BIN\XCDROM.SYS /D:FDCD0001 /H
SHSUCDX /D:FDCD0001,X /Q

DEVLOAD /Q /H C:\FDOS\BIN\XCDROM.SYS /D:FDCD0001 /H
SHSUCDX /D:FDCD0001,X /Q
=======================

But SHSUCDX /D then reports X: and Y: as the drive assignments, and only Y: works. X: produces the error I first reported.

So it's not entirely clean and clear, but have I just arrived at the best workaround?

On 5/18/2015 3:50 PM, Don Flowers wrote:
John, actually you probably don't need to unload shsucdx, like you I used that command line from my install (I used the all_cd.iso).

On Mon, May 18, 2015 at 3:29 PM, John Hupp <free...@prpcompany.com <mailto:free...@prpcompany.com>> wrote:

    Point well taken about diskinit and a consistent drive assignment,
    though in this case it will probably not matter.

    I don't have any plan to boot CDROM images on this -- the
    FDBOOTCD.ISO command was just part of the auto-installed
    configuration.

    If I substitute SHSUCDX /D:FDCD0001,X /Q in both locations below,
    I then can access the drive as Y: (the same behavior as FDCD0001,D
    resulting in access as E:).

    What I don't understand is why I have to unload SHSUCDX and then
    re-run the same two commands as above the unload.


    On 5/18/2015 2:58 PM, Don Flowers wrote:
    If you have other partitions they will always be "seen" by
    FreeDOS diskinit before any of your drivers are loaded therefore
    it is best to reassign your drive letter. FreeDOS 1.1 uses a
    default of X: and I follow that assignment. This will result in a
    consistent drive assignment for your CD. Also unless you plan on
    regularly booting CDROM images as opposed to real "burned"
    CD-ROMs, the simplified files I sent are adequate for everyday use.

    On Mon, May 18, 2015 at 2:48 PM, John Hupp
    <free...@prpcompany.com <mailto:free...@prpcompany.com>> wrote:

        Taking the next obvious step, I can even successfully
        condense the last 5 lines as below (which lets me access the
        drive as E:, not D:), but I have not succeeded beyond that.

        =======================
        REM (some commands)

        SHSUCDX /QQ /D3
        LH SHSUCDHD /QQ /F:FDBOOTCD.ISO

        REM (some commands)

        REM DEVLOAD /H /Q %dosdir%\BIN\UIDE.SYS /H /D:FDCD0001 /S5

        DEVLOAD /Q /H C:\FDOS\BIN\XCDROM.SYS /D:FDCD0001 /H
        SHSUCDX /D:FDCD0001,D /Q

        SHSUCDX /QQ /U
        DEVLOAD /Q /H C:\FDOS\BIN\XCDROM.SYS /D:FDCD0001 /H
        SHSUCDX /D:FDCD0001,D /Q
        =======================

        (And yes, fdconfig.sys does have LASTDRIVE=Z.)



        On 5/18/2015 2:17 PM, John Hupp wrote:
        Thanks, that sort of works. Based on the cdrom.bat commands,
        this snippet from my current autoexec.bat works:

        =======================
        REM (some commands)

        SHSUCDX /QQ /D3
        LH SHSUCDHD /QQ /F:FDBOOTCD.ISO

        REM (some commands)

        REM DEVLOAD /H /Q %dosdir%\BIN\UIDE.SYS /H /D:FDCD0001 /S5

        DEVLOAD /H /Q %dosdir%\BIN\XCDROM.SYS /H /D:FDCD0001
        SHSUCDX /QQ /~ /D:?SHSU-CDR,D /D:?SHSU-CDH,D /D:?FDCD0001,D
        /D:?FDCD0002,D /D:?FDCD0003,D

        SHSUCDX /QQ /U
        DEVLOAD /Q /H C:\FDOS\BIN\XCDROM.SYS /D:FDCD0001 /H
        SHSUCDX /D:FDCD0001,D /Q
        =======================

        With this, I can access the cdrom as E: (not D:).

        But I have not been able to merge the last 5 command into
        just 2 or 3.  Among many attempts, I think I tried just
        running the last 3 of the 5 and that failed as before.  What
        am I not seeing?

        On 5/18/2015 10:53 AM, Don Flowers wrote:
        One of these two should work. These are batch files so
        rename them accordingly.

        On Mon, May 18, 2015 at 10:35 AM, Don Flowers
        <donr...@gmail.com <mailto:donr...@gmail.com>> wrote:

            Is it a slave or secondary master drive?

            On Mon, May 18, 2015 at 10:30 AM, John Hupp
            <free...@prpcompany.com
            <mailto:free...@prpcompany.com>> wrote:

                Thanks for the idea and an interesting web page,
                but this is a plain old IDE CD-ROM.


                On 5/18/2015 10:10 AM, Don Flowers wrote:
                http://www.rmprepusb.com/tutorials/winimage

                On Mon, May 18, 2015 at 10:08 AM, Don Flowers
                <donr...@gmail.com <mailto:donr...@gmail.com>> wrote:

                    If you have a AHCI/SATA CD/DVD drive, try
                    downloading the FreeDOS - SATA for Ghost disk
                    here, extract the AHCI.SYS driver and use the
                    following configuration.
                    @ECHO OFF
                    SHCDX86.COM <http://SHCDX86.COM> /QQ /U
                    IF NOT EXIST CDROM001 DEVLOAD /Q /H
                    C:\FDOS\BIN\AHCI.SYS /D:CDROM001 /H
                    IF NOT EXIST CDROM001 DEVLOAD /Q /H
                    C:\FDOS\BIN\UIDE.SYS /D:CDROM001 /H
                    IF EXIST CDROM001 SHCDX86.COM
                    <http://SHCDX86.COM> /D:CDROM001,X /Q


                    On Mon, May 18, 2015 at 10:04 AM, John Hupp
                    <free...@prpcompany.com
                    <mailto:free...@prpcompany.com>> wrote:

                        I tried updating to the latest uide.sys from
                        
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/ellis/,
                        but
                        I get the same error.

                        I also get the same error with the last
                        version of xcdrom.sys.

                        Next-best solutions?

                        On 5/16/2015 5:34 PM, John Hupp wrote:
                        > Hi, all.
                        >
                        > It's been some years since I've been
                        active on this list, but I hope
                        > you can come through for me again now.
                        >
                        > I installed 1.1 from the bootable CD,
                        but from the installed DOS, I
                        > can't access a CD-ROM.  I get "Error
                        reading from drive D: data area:
                        > drive not ready."
                        >
                        > I found this for VirtualBox:
                        >
                        
http://www.freedos.org/wiki/index.php/VirtualBox_-_Chapter_12#Known_Bugs:_6._CD_changes_are_not_detected
                        >
                        > For real hardware, is the XCDROM
                        workaround the best solution?



        
------------------------------------------------------------------------------
        One dashboard for servers and applications across
        Physical-Virtual-Cloud
        Widest out-of-the-box monitoring support with 50+ applications
        Performance metrics, stats and reports that give you
        Actionable Insights
        Deep dive visibility with transaction tracing using APM Insight.
        http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
        _______________________________________________
        Freedos-user mailing list
        Freedos-user@lists.sourceforge.net
        <mailto:Freedos-user@lists.sourceforge.net>
        https://lists.sourceforge.net/lists/listinfo/freedos-user




    
------------------------------------------------------------------------------
    One dashboard for servers and applications across Physical-Virtual-Cloud
    Widest out-of-the-box monitoring support with 50+ applications
    Performance metrics, stats and reports that give you Actionable Insights
    Deep dive visibility with transaction tracing using APM Insight.
    http://ad.doubleclick.net/ddm/clk/290420510;117567292;y


    _______________________________________________
    Freedos-user mailing list
    Freedos-user@lists.sourceforge.net  
<mailto:Freedos-user@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/freedos-user


    
------------------------------------------------------------------------------
    One dashboard for servers and applications across
    Physical-Virtual-Cloud
    Widest out-of-the-box monitoring support with 50+ applications
    Performance metrics, stats and reports that give you Actionable
    Insights
    Deep dive visibility with transaction tracing using APM Insight.
    http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
    _______________________________________________
    Freedos-user mailing list
    Freedos-user@lists.sourceforge.net
    <mailto:Freedos-user@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/freedos-user




------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y


_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to