T.R | Title | User | Personal Name | Date | Lines |
---|
747.1 | | DECWET::COLGATE | | Thu Nov 02 1995 09:18 | 8 |
747.2 | updated hal list | ATZIS1::BACHNER_H | Mouse not found. Click OK to continue | Thu May 15 1997 09:08 | 26 |
| I've updated the list af HALs but found a few for which I don't know the
hardware they support. Can someone fill the holes, please ?
hal0jens.dll AXP PC 150 or 2000
halalcor.dll AlphaStation 500, 600
halalp.dll
halavant.dll AlphaStation 200/250/400,
Alpha XL 2xx/Powergrade; AlphaServer 400 ?
haleb164.dll EB164 board (evaluation board)
haleb64p.dll EB64 board (evaluation board)
halflex.dll
halgammp.dll AlphaServer 2x00(A) 5/250
hallego.dll
hallx3.dll AlphaStation 255
halmiata.dll Personal Workstation 433a, 500a
halmikas.dll AlphaServer 1000 4/xxx
halnonme.dll E&RT board (Noname)
halpinna.dll AlphaServer 1000(A) 5/xxx
halqs.dll Multia
halrawmp.dll AlphaServer 4100
halsabmp.dll AlphaServer 2x00(A) 4/xxx
haltimbr.dll
halxl.dll Alpha XL 3xx
Thanks,
Hans.
|
747.3 | | DECWET::LEESC | | Thu May 15 1997 09:48 | 11 |
| halalp.dll - Alpha OEM hal. I am not sure which OEM it is.
halavant.dll - add AlphaServer 300 and AlphaServer 400.
halflex.dll - Alpha OEM hal. I am not sure which OEM it is.
hallego.dll - E&RT PICMG board (Lego).
halmikas.dll - add AlphaServer 1000A 4/xxx.
halpinna.dll - add AlphaServer 800 and AlphaStation 600A
haltimbr.dll - Alpha OEM hal. I am not sure which OEM it is.
Scott
|
747.4 | changes incorporated | LNZALI::BACHNER | Mouse not found. Click OK to continue | Fri May 16 1997 01:51 | 23 |
| Thanks. Here's the updated list:
hal0jens.dll AXP PC 150 or 2000
halalcor.dll AlphaStation 500/600
halalp.dll Alpha OEM hal
halavant.dll AlphaStation 200/400, Alpha XL 2xx/Powergrade,
AlphaServer 300/400
haleb164.dll EB164 board (evaluation board)
haleb64p.dll EB64 hudson board (evaluation board)
halflex.dll Alpha OEM hal
halgammp.dll AlphaServer 2x00(A) 5/250
hallego.dll E&RT PICMG board (Lego)
hallx3.dll AlphaStation 255
halmiata.dll Personal Workstation 433a, 500a
halmikas.dll AlphaServer 1000(A) 4/xxx
halnonme.dll E&RT board (Noname)
halpinna.dll AlphaServer 1000(A) 5/xxx, AlphaServer 800,
AlphaStation 600A
halqs.dll Multia
halrawmp.dll AlphaServer 4100
halsabmp.dll AlphaServer 2x00(A) 4/xxx
haltimbr.dll Alpha OEM hal
halxl.dll Alpha XL 3xx
|
747.5 | | BGSDEV::MORRIS | Tom Morris - Light & Sound Engineering | Fri May 16 1997 02:21 | 2 |
| halalp.dll is probably an Alpine system.
halflex.dll is likely to be a Deskstation Raptor Reflex
|
747.6 | Where are they? | NWD002::SKRABUT_LA | Larry Skrabut | Mon May 19 1997 06:46 | 10 |
| Question: I am under the impression that there are different hal's
for NT 3.51 and 4.0 if needed, rather than "Out of the box" hal's.
What hal's are these for?
Where would these be located by these names? Web pointer:
http://www.windows.digital.com/support/sysoft.asp
but the names are not what has been posted by the preceding replys.
|
747.7 | | TARKIN::LIN | Bill Lin | Mon May 19 1997 07:26 | 18 |
| re: .6 by NWD002::SKRABUT_LA
Hi Larry,
I don't understand your confusion. I did a quick check of the
AlphaServer 4100. On the
http://www.windows.digital.com/support/sysoft.asp page, there is
section for AlphaServer 4100 and the 3 current models. All three point
to a single AlphaServer 4000 page, with separate ZIP files for NT 3.51
and NT 4.0, and a single ZIP file for the AlphaBIOS. These ZIP file
*names* are inconsequential. Download the files, and you'll see the
.DLL file names within the ZIP kits. I see halrawmp.dll in the ZIP
files. Yes, the halrawmp.dll files are different for 3.51 vs. 4.0, as
are the txtsetup.oem files as one would expect.
Cheers,
/Bill
|
747.8 | Same names for the product across the versions | NWD002::SKRABUT_LA | Larry Skrabut | Tue May 20 1997 06:55 | 9 |
| re: .7
Bill, Now looking around I now understand that the "hal's" are named
the same for the product across the NT versions. This is the fine point
I was missing on the start of the post. Of course the names are buried
within the zipped files on the web site and are of no real use to the
end user per say.
Thanks of clearing this up for me, Larry S.
|