home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.sys.cisco
- Path: sparky!uunet!boulder!recnews
- From: C.Chaundy@its.unimelb.edu.au
- Subject: Re: Finding ROM version
- Message-ID: <726885710.5170@news.Colorado.EDU>
- X-Vms-Cc: IN%"cisco@spot.Colorado.EDU"
- Sender: news
- Content-Transfer-Encoding: 7BIT
- Mime-Version: 1.0
- Date: 13 Jan 1993 09:53:59 +1100
- Approved: news
- X-Vms-To: IN%"remaker@cisco.com"
- X-Note1: message-id generated by recnews
- X-Note2: mail msgid was <01GTGS2OVJLK8WVZ1M@ucsvc.ucs.unimelb.edu.au>
- Lines: 37
-
- >Date: 12 Jan 1993 09:46:39 -0800 (PST)
- >From: Phillip Remaker <remaker@cisco.com>
- >Subject: RE: Finding ROM version
- >
- >It looks like you can't!
- >
- >You can "infer" it from the bootstrap version, but not exactly.
- >
- >Why is this information important? I can put in an enhancement
- >request.
-
- I understand that there are certain restrictions that affect what versions
- can be Flash booted (or TFTP booted for that matter) depending on the ROM
- software version. It would be nice to know what version ROM software that
- you have so you can be certain that Flash images you create will boot, so
- yes, could you put in an enhancement request?
-
- >>
- >> If your system has been booted from Flash EEPROM, is there a way to
- >> find out what version system is resident in the ROMs in the system
- >> (without reloading the system of course :-)?
- >>
- >> Regards, Chris Chaundy (Technical Manager, Networks)
- >>
- >> Information Technology Services, Thomas Cherry Building,
- >> The University of Melbourne, Parkville, Victoria 3052 Australia
- >> Phone: +61 3 344 7045 Fax: +61 3 347 4803
- >> Internet: C.Chaundy@its.unimelb.EDU.AU (X.121 505233430003)
- >>
- >
- >
- >--
- >Phillip A. Remaker remaker@cisco.com
- >cisco Systems Customer Engineering 800-553-24HR
- >1525 O'Brien Drive Menlo Park, CA 94025
-
- Regards, Chris Chaundy
-