• Industries
  • Products
  • Buy
  • Services & Support
  • Communities
  • Discussion Groups

    Installation & Licensing

    Reply
    *Martin, Jason

    A2K Network Installation to Netware 4.11 server

    123 Views, 2 Replies
    10-27-1999 08:47 PM
    Most of this is something of a cross post from the adt 2 newsgroup, sorry to
    those of you that read both.

    Here's what I want to do:
    I'd need to do a network install of adt2 to a Netware 4.11 server. In the
    netsetup I set to network location to \\servername\volume\foldername

    I'd need to use an NT server as a license server for adt. License manager
    is already setup and running on the NT server.

    On the license manager setup I'm selecting Install License manager later.
    If I select IPX support I can't see the license server.
    If I select TCP/IP support adt will kindof launch but no arx anywhere will
    load. If I try to load any arx I get "AcRxDynamicLinker failed to load
    \\servername\volume\foldername\arxname.arx'
    \\servername\volume\foldername\acad.exeRegenerating model."

    If I install to an NT server then adt seems to run. The only problem is I
    must install adt to the nw server.

    If the installation path is the netware server, the network deployment setup
    will not work. When I click on the setup.exe I get an alert box that says
    "Could not find files required to install AutoCAD. Contact your network
    administrator or CAD manager for assitance.

    I compared the NT network installation and the Netware network installation.
    I found that the only files that were different were the following:
    acad2000.cfg
    deisl1.isu
    desktop.arg
    \plot styles\add-a-plot styel table wizard.lnk
    \plotters\add-a-plotter wizard.lnk
    \support\acad.mnc
    \support\aecarchx.dll
    \support\aecarchx.mnc
    \support\aecarchx.mns

    Most of these aren't a problem but the aecarchx.dll concerned me a little.
    I don't have any C background so debugging the dll is beyond me but looking
    at the dll in quick veiw reveals the following differences:
    Novell Server NT Server
    Checksum:00000000 Chekcsum:0003ac75
    Nothing VA-Bound Import:0298
    Nothing Size-Bound Import:0044

    Even worse I just found this
    http://www.autodesk.com/support/solutions/34763.htm . My initial read of
    this leads me to believe that Autodesk has dropped support of installation
    to anything but an NT server???

    If anyone has gotten a2k, or actually adt2 to work in a network install on
    an netware server please let me know what simple steps I've been missing.

    TIA

    jason martin
    frankfurt-short-bruza
    Please use plain text.
    *Milana, Jerry

    Re: A2K Network Installation to Netware 4.11 server

    10-28-1999 07:04 PM in reply to: *Martin, Jason
    Jason,

    It sounds like you may not have long file name support installed on your netware
    server.

    Jerry Milana,
    Autodesk Product Support

    Jason Martin wrote:

    > Most of this is something of a cross post from the adt 2 newsgroup, sorry to
    > those of you that read both.
    >
    > Here's what I want to do:
    > I'd need to do a network install of adt2 to a Netware 4.11 server. In the
    > netsetup I set to network location to \\servername\volume\foldername
    >
    > I'd need to use an NT server as a license server for adt. License manager
    > is already setup and running on the NT server.
    >
    > On the license manager setup I'm selecting Install License manager later.
    > If I select IPX support I can't see the license server.
    > If I select TCP/IP support adt will kindof launch but no arx anywhere will
    > load. If I try to load any arx I get "AcRxDynamicLinker failed to load
    > \\servername\volume\foldername\arxname.arx'
    > \\servername\volume\foldername\acad.exeRegenerating model."
    >
    > If I install to an NT server then adt seems to run. The only problem is I
    > must install adt to the nw server.
    >
    > If the installation path is the netware server, the network deployment setup
    > will not work. When I click on the setup.exe I get an alert box that says
    > "Could not find files required to install AutoCAD. Contact your network
    > administrator or CAD manager for assitance.
    >
    > I compared the NT network installation and the Netware network installation.
    > I found that the only files that were different were the following:
    > acad2000.cfg
    > deisl1.isu
    > desktop.arg
    > \plot styles\add-a-plot styel table wizard.lnk
    > \plotters\add-a-plotter wizard.lnk
    > \support\acad.mnc
    > \support\aecarchx.dll
    > \support\aecarchx.mnc
    > \support\aecarchx.mns
    >
    > Most of these aren't a problem but the aecarchx.dll concerned me a little.
    > I don't have any C background so debugging the dll is beyond me but looking
    > at the dll in quick veiw reveals the following differences:
    > Novell Server NT Server
    > Checksum:00000000 Chekcsum:0003ac75
    > Nothing VA-Bound Import:0298
    > Nothing Size-Bound Import:0044
    >
    > Even worse I just found this
    > http://www.autodesk.com/support/solutions/34763.htm . My initial read of
    > this leads me to believe that Autodesk has dropped support of installation
    > to anything but an NT server???
    >
    > If anyone has gotten a2k, or actually adt2 to work in a network install on
    > an netware server please let me know what simple steps I've been missing.
    >
    > TIA
    >
    > jason martin
    > frankfurt-short-bruza
    Please use plain text.
    *Martin, Jason

    Re:

    10-28-1999 07:36 PM in reply to: *Martin, Jason
    Long file names are enabled on the server. We're running R14 and S8 from
    the same vol. on the nw server, which also requires long file names. Any
    other ideas???

    jason martin
    frankfurt-short-bruza

    Jerry Milana wrote in message <38190096.87C38B77@autodesk.com>...
    >Jason,
    >
    >It sounds like you may not have long file name support installed on your
    netware
    >server.
    >
    >Jerry Milana,
    >Autodesk Product Support
    >
    Please use plain text.