|
Upgrade FAQ |
AMOS 8.0 |
Last technical update: 20-February-2004
This FAQ (Frequently Asked Questions) covers upgrading a site to AMOS 8.0, used only on the new, super fast, AM-8000 and Eagle 800 systems.
For the MOST CURRENT version of this FAQ, browse to AMPM.AlphaMicro.com/AMPM/8kFAQ.htm.
In the recommended configuration, AMOS Hard Drives are actually .AMD files on the embedded file system (usually NTFS). As such, there can be multiple .AMD "AMOS drives" on one physical hard disk. On the standard system, about 5GB is reserved for various embedded and "warmboot" like functions. Thus the current standard 18GB drive actually has between 12GB and 13GB of space for one or more .AMD "AMOS drives". For example, the base 18GB drive in an AM-8000 could be configured to have a 2GB "DSK:" and a 9GB "SUB:". Within these .AMD "pseudo hard disks", all of the label, bitmap, directory, block links, data, etc. are identical to AMOS formatted hard disks. This is why all of the disk related software works right.
These .AMD files themselves can be copied as is, providing a complete image backup. And, if on a supported file system, the copies can be defined for AMOS 8.0 and accessed directly, like any AMOS disk. And doing this copy with the embedded software is FAST: about 2 minutes per GB.
Using some of the embedded support (Norton's Ghost), a DOS style partition with one or more .AMD files can be compressed onto another partition (<2 min/GB) or a CD or DVD. Individual .AMD files can be restored from these compressed partitions and then accessed directly from AMOS 8.0.
With these choices, the 4GB size of a DVD should be considered when planning the AMOS "disk drive" configuration. - 9-November-2003
As shipped, we set aside just over 4GB for the Embedded software and System recovery. With the 18GB standard hard disk, this leaves just under 13GB (call it 12GB) for AMOS .AMD disk space. Currently, this space is meant to be configured by the dealer. It can be configured as one 12GB AMOS .AMD disk or divided into smaller AMOS .AMD disks (each with a different size!). - 9-November-2003
If you are upgrading from a system with two 2GB disks, DSK0:-4 and DSK5:-9:, create one 4GB .AMD "pseudo AMOS disk" with a 10 logical split, giving DSK0:-9:. All of your software will work just the same. - 9-November-2003
This process creates a formatted AMOS .AMD pseudo drive on one of the NTFS formatted partitions and links it, via a three letter device name, with AMOS. The process is divided into these parts:
On the embedded side, create and name the .AMD pseudo drive:
Open "AMOS Disks" tab of the "AM8000 Configuration" screen.
Then <Browse>, instead of <Create>, to add that new file to the "Amos Disks" lists and continue with the rest of this procedure.]
On the AMOS side, create a driver and modify the system .INI file:
Initialize the new logicals:
DO INITC.DSK TST1 will initalize logicals TST100: thru TST199:.
(create and use "DO INIT.DSK devnnn:"
for each logical "devnnn:".)
; INIT.DSK -- Initialize a logical disk
; (C) Copyright 2004 by Alpha Microsystems
;
; usage: DO INIT.DSK devn:
; where devn is the exact device to be initalized.
:T
if device("$0")
Sysact $0
i
y
y
e
Label $0
init.dsk $0
$0
init.dsk $0
init.dsk $0
init.dsk $0
Mount $0
else
EXIT
endif
; INIT10.DSK -- Initialize 10 logical disks
; (C) Copyright 2004 by Alpha Microsystems
;
; usage: DO INIT10.DSK devn
; where devn is part of devnx:
:T
if device("$00:")
do init.dsk $00:
do init.dsk $01:
do init.dsk $02:
do init.dsk $03:
do init.dsk $04:
do init.dsk $05:
do init.dsk $06:
do init.dsk $07:
do init.dsk $08:
do init.dsk $09:
:<
Done with the $00s!
>
else
EXIT
endif
; INITC.DSK -- Initialize all logicals of a dev:
; (C) Copyright 2004 by Alpha Microsystems
;
; usage: DO INIT.100 devn
; where devn is part of devnxx:
:T
if device("$00:")
do init10.dsk $00
do init10.dsk $01
do init10.dsk $02
do init10.dsk $03
do init10.dsk $04
do init10.dsk $05
do init10.dsk $06
do init10.dsk $07
do init10.dsk $08
do init10.dsk $09
:<
Done with the $000s!
>
else
EXIT
endif
(As part of the xAdmin package, they have been improved since inserted above.)
Your new device is now ready to use. - 21-October-2003 - 20-February-2004
For the most part, this is just the same as with any AMOS hardware upgrade:
While you can order a tape drive, or install an older SCSI tape drive, in the AM-8000, you can also move your current AMOS SCSI disk drive to the AM-8000 as a secondary drive. Then use COPY/NOD or MTURES/NOD to put the files to the new disk and setup your new .INI file. The following procedure covers either method:
Either way, here are the steps that need to be taken, with the few AM-8000 differences in italics:
If the old SCSI device is 50 pin, you will need a PDB-00440-91 Wide SCSI Adapter: 50-pin device to 68-pin bus.
Make a good backup!
Determine the SCSI ID you will use. Remember, if there is a SCSI ID conflict, the system will probably not boot!
Install the SCSI device in the AM-8000 chassis (usually in the upper bay, using the SCSI channel "B" cable, the one that usually continues on to the back of the chassis.):
Once the devices are installed and powered up, map the desired SCSI drive to the desired AMOS SCSI ID on the "Scsi Devices" tab of the "AM8000 Configuration" screen. (This is not as complicated as trying to describe it.)
That screen is divided into a top and bottom section.
The top section, in outline format, should list each SCSI type bus (including IDE buses) and each SCSI type of device. You should see the primary disk drive on the first of the "adpu320" buses. The device you just added should be on the second "adpu320" bus. You should also see the DVD/CD drive on one of the "atapi" (IDE) buses.
The bottom section lists 7 possible AMOS SCSI ids and indicates which of the above items are mapped to which AMOS SCSI ID. You should see the DVD/CD drive already mapped to one of those IDs. (You should NOT see the primary disk drive on the bottom half - it is not an AMOS SCSI device.)
With a mouse, drag the device you just added from the top half of the screen to the desired ID on the bottom half.
Remember to write the changes to the Registry (see the last item about the "AM8000 Configuration" screen).
If you shut down AMOS, press the reset button to re-boot the system.
Create a driver:
Modify your test.INI and reboot:
If it is a tape drive, be sure there is a "DEVTBL /dev" or similar line in your test.INI.
If it is a hard disk, in the test .INI:
Exit with a G to MONTST the modified .INI.
For years, it has been wise to always let the AMOS disk caches and hardware drive caches flush before turning off the power. My personal suggestion has been to MONTST into a short .INI before turning off the power.
With the AM-8000, we suggest a more formal shutdown of the Shutdown option in the File menu of the AM-8000 System screen. This will automatically do a software and soft power shutdown. However, if you are using AMOS SCSI disk drives, the safest procedure would begin, as above, with a MONTST to flush the AMOS disk cache.
As a side note: In all of our testing of the AM-8000, DSKANA has fixed any problems where powering down was the apparent cause, but don't count on it - use a UPS!
SE vs. LVD devices:
We call the AMOS formatted drive on older AMOS systems "AMOS SCSI". These are drives completely formatted for AMOS. On the AM-8000, we are taking advantage of other, more flexible and optimized file systems, usually NTFS. The .AMD drives, begun as part of the AMPC product, are simply binary disk files, each representing a physical AMOS SCSI disk. They can be emailed, ftped, etc., and stored on almost any type of system, including AMOS. Inside, they are structured like regular AMOS SCSI drives. The AM-8000's AMOS booting DSK: device MUST reside on a .AMD drive.
AMOS SCSI vs. .AMD:
Both .AMD devices and AMOS SCSI devices are logically mapped to AMOS 8.0. This mapping is done from the "AM8000 Configuration" screen:
AMOS SCSI devices are mapped to virtual SCSI IDs using the "Scsi Devices" tab - in AMOS use FIXLOG and the SCZPC.DVR.
.AMD devices are mapped directly to device names using the "AMOS Disks" tab - in AMOS just COPY dev=PCDSK.DVR.
(Sorry for the tab name confusion: the screens were designed and in the field long before we moved to this AMOS SCSI/.AMD naming scheme.)
The existing MTUSAV style backups are fully supported on the AM-8000. However, they are about the same speed as on earlier systems. To significantly reduce the backup time, consider the following (which may influence the disk configuration you select.):
AMOS DVD-RAMs, as well as CDs and CD-RWs, made on older AMOS systems are readable on the AM-8000. However, DVD-RAMs and similar media written on the AM-8000 use the .AMD files described above and thus are not readable on older AMOS systems.
While MAKDVD (and MAKACD) is currently not supported on the AM-8000, the AM-8000's alternatives are more flexible, including allowing different size "AMOS drives" on the same DVD. In addition, DVD-R media can be used to create more permanent backups.
When using TRANS or RETRV with AMOS 8.0 on the remote system, use the /NOHOG switch.
Within COMM, make sure JWAIT (upper right) is ON and that FLOW HW ON. Usually, this is handled in the TALK.INI with $FLOW ON and $JWAIT. - 10-February-2004
"SLAVE.LIT" currently only works correctly on the PCCOM serial ports.
Within AUTLOG, be sure to SET FLOW RTS as RTS/CTS hardware flow control is required for reliable behavior. (And make sure the cabling supports the flow control.) - 10-February-2004
Not since a recent Embedded Update
(ftp.AlphaMicro.com/anon/UEMBED.TXT)!
Yes, but we are working to simplify them so we will cover that
individually for the time being. -
10-February-2004
Serial ports and telnet sessions have no new limits. The console
virtual terminals have no special limits - some of us are now routinely using
6200. The console virtual terminals currently have the following
TRMDEF buffer size limits: 258, 510, 510. No error message if larger, just
problems. -
10-February-2004
The PCI 4 (PFB-00131-04) and 8 (PFB-00131-08) port PCI COM cards, USB serial ports, as well as the two COM ports that are part of the system, are all DB-9M with the IBM PC pin-outs. (Be aware that most of PCI COM card DB-9M connectors on at the end of octopus cables.) - 21-October-2003 - 10-February-2004
Also be aware that, with nothing wired into a COM port, it's flow control defaults to "busy" and output will backup inside the AM-8000. If this is a serious problem, the hoods listed below can be modified with 1K to 10K ohm resistors. This should be done with caution as the net effect depends upon both the specific circuits on that port in the AM-8000 and in the equipment at the other end (terminal, modem, PC, etc.). - 21-October-2003
The DWB-10317-25 converts the standard PC connectors (DB-9M) to Alpha Micro RJ-45 style, making them compatible with AM-359 cables (page 2 of the AM-8000 price list.).
If you need to plug into the older Alpha Micro AM-355 style DB-9Fs, the PDB-00359-50 cable set (eight 4-foot cables per package - section I -50 of the regular price book) will convert AM-359 style RJ-45 serial ports to the standard Alpha Micro DB-9F pin out.
AMOS 8.0 uses Microsoft's XP Embedded OS for many supporting services, including low level networking. In previous versions, AMOS has been immune to network related viruses. Many have asked:
"What are the virus like risks of using AMOS 8.0 over this Microsoft environment?"
The answer is:
"Keep it as an AMOS machine and AMOS 8.0 remains as immune as all other AMOS machines."
Specifically, AMOS's new immunity depends upon:
The Microsoft features we install and activate:
We only install and activate Microsoft features needed to support AMOS 8.0. There is no Microsoft Web Server, no Microsoft Email, etc. The only Microsoft feature we have had to install and activate that is vulnerable (if we did not install the firewall - below) is RPC services. The way we have it installed, attacks on it simply disable it, causing no problems with AMOS - just temporary XP Embedded administrative problems. (Reboot and even that problem disappears.) What is installed but disabled is Microsoft File and Printer sharing. Enabling parts of these is under the control of the system administrator - AMOS 8.0 works fine without them.
The XP Embedded's firewall configuration:
XP Embedded includes a basic firewall. This firewall has no effect on AMOS 8.0 network traffic but can be used to totally isolate the XP Embedded from any network traffic. We normally ship it with just a few ports open, including those necessary to support Microsoft file and printer sharing IF later enabled by the system administrator. Or the system administrator can simply close all ports.
Patches available from Microsoft:
As patches are made available from Microsoft, we incorporate them into future builds. However, only a few even apply to the components we install. Because the XP Embedded features are "locked down" at build time for each machine, the machine would have to be rebuilt here at the factory to install most patches. That is just part of the Microsoft design of XP Embedded.
We left our own AM-8000.AlphaMicro.com demonstration system on the Internet WITHOUT ANY firewall for months last year. AMOS was never damaged! The RPC service attacks were annoying because they interfered with our testing and learning by stopping us from changing the XP (not the AMOS) disk configuration - we had to reboot to make the changes. Since re-activating the XP Embedded's firewall on the XP Embedded's Internet interface, we have had no virus related issues. If someone wants to hammer at that interface, it is 66.166.1.35. Please let us know if you see any weaknesses!
(The AM-8000 has two interfaces. We left the second one on our private network with some firewall holes for Microsoft print and file sharing.) - 10-February-2004
From an AMOS console VTM (Virtual Terminal):
If we told you that, we'd have to shoot you!
Actually, there are a number of "hidden" areas, only the first of which should be accessed by dealers and administrators:
At the system console:
When MONTSTing, you may notice that the MONTST arguments get TODOSed. This provides backup copies and maintains consistency. When you modify a system.INI file, always MONTST (or TODOS system.INI) to update the second copy, especially the AM8000.INI, which is used by AM8000.EXE on the first boot.
As a note about safety, the MONTST procedure always transfers using the AMOS file name (6.3 format). We also provide backup copies the original AM8000.MON and AM8000.INI files using longer file names so they will not be accidentally erased by any normal AMOS user procedure.
A lot of old AMOS software is not needed and some will generate serious errors. Much of this is for obsolete hardware, such as STR.DVR shipping with the driver for hardware that has not been made for about 20 years. We have taken this opportunity to clean out this old software from AMOS. However, if you may put this software back on when upgrading from an older AMOS system. We have included OPR:ERAS8K.DO to help you clean out these old files. We strongly recommend that, after you have done an MTURES/NOD (for example), you log to OPR: and DO ERAS8K.DO. Please remember that some of these old files can damage your AMOS 8.0 system - using this OPR:ERAS8K.DO is a reasonable safety precaution. - 11-February-2004
Yes, just as on other AMOS systems.
This is the same SSD chip as used on other modern AMOS systems.
If you are upgrading a modern AMOS system, simply move the SSD chip.
All of the AMOS programming is identical - NO changes necessary.
AMOS 8.0 requires a different PIC than previous AMOS versions.
All other applications, from Alpha Micro or from other vendors, should work without needing new PICs.
The little stuff to watch out for (may not be specific to AMOS 8.0).
The following third part programs have been reported as working, not working, or with special limitations under AMOS 8.0. Please note that these are just reports. Alpha Microsystems does not support any of these programs. For more details, contact the manufacturer. - 10-February-2004
TALKTO.LIT - does not work - per Birmingham Data System - 10-February-2004
AutoLog - works with this known restriction:
SLAVE.LIT - works on the PCCOM ports, does not work on the SIO ports - per Alpha Microsystems. - 10-February-2004
SSD Protector 2.8 - both PIC.LIT and CODE.LIT works - per Jacob Levine, Levicom Sistemas SC, Mexico - 10-February-2004
SFORCE - both versions 1.0(112) and 2.2(135) work. - 10-February-2004
MetropoliS - works - 10-February-2004
SuperVUE - works. - 10-February-2004
DataVUE - does not work (source was WD-16, but their crossassembler is no longer available). - 10-February-2004
IMS [specifically version 5.0(18)] works - per Paul Richardson, Stage Electrics - 11-February-2004
If you have additional questions about upgrading to an AM-8000, please click here and drop us a line. We will always answer your questions and it may become part of this FAQ.
Additional AM-8000 information:
The following changes have been made to the document, most recent first:
|
Copyright (C) 2003 by Alpha Microsystems.