InfoServer 100 trouble
g...@decadence.it
I've got an InfoServer 100 and I wanted to bring it back to life.
Bad surprise, I cannot boot from its harddisk.
I also tried to boot it by the VMS 5.5 and 7.2 install CDROMs but I was
unsuccesful.
But the same CDROM drive and VMS media works fine on another MicroVAX.
Local tests went all good, and no error is reported: both 'test 0' and
'test 50' report everything is fine (I compared results with tables from a
VAXstation 3100 manual)
I've done a clean install of OpenVMS 5.5 on another MicroVAX which can
boot and work well with that disk.
The same disk doesn't work on the InfoServer.
Simply, when I issue boot command, the system prints the disk name and the
keeps the cursor blinking until forever.
>>> BOOT DKA400
-DKA400
What's wrong?
Is the InfoServer faulty?
Or I am missing something?
I used a standard VMS 5.5 hobbyist distribution for installing.
Does the Infoserver need a different install media?
Any help is welcome! :)
Thanks
gl
tomars...@comcast.net
Do a show dev on the Infoserver
then check for this
>>> Set halt 2
>>> set boot dka100,dka200
>>> set bflg d0000000
If your InfoServer has the standard RZ23/24 it should be DKA0 then just
do a
>>> b -> with no device after the b
But make sure the above commands are correct. The default password for
the InfoServer 100 is ess
Hope this helps
phil
Peter Weaver
news:pan.2006.06.04....@decadence.it...
> Hello everyone!
>
> I've got an InfoServer 100 and I wanted to bring it back to life.
> Bad surprise, I cannot boot from its harddisk.
>
> I also tried to boot it by the VMS 5.5 and 7.2 install CDROMs but I
> was
> unsuccesful.
The InfoServer will not boot VMS (unless there is some hack I don't
know about), it boots its own little Operating System that serves out
the CDs and disk partitions. I do not know where you can get the
InfoServer software these days. If you have access to a newer Alpha of
IA64 version of VMS you can do the same thing with;
$ mcr ess$infoserver
InfoServer> help
Information available:
Class_Names CREATE DELETE Device_Names
EXIT
HELP Partition_Names SAVE SHOW SPAWN
Wildcards
Topic?
g...@decadence.it
> The InfoServer will not boot VMS (unless there is some hack I don't
> know about), it boots its own little Operating System that serves out
This is really curious. Is it a first attempt to DRM-like protection?
I mean, is there anything in the hardware or firmware that blocks from
booting other operating system?
> the CDs and disk partitions. I do not know where you can get the
> InfoServer software these days. If you have access to a newer Alpha of
> IA64 version of VMS you can do the same thing with;
>
> $ mcr ess$infoserver
> ...
This is very useful since I have an alpha running VMS.
Thanks for the information!
gl
g...@decadence.it
> Try this
> Do a show dev on the Infoserver
The InfoServer came to me with a RZ23 as DKA400 and a non-DEC CDROM as
DKB300.
It is a must that the RZ23 should be DKA0 ?
> then check for this
>>>> Set halt 2
>>>> set boot dka100,dka200
>>>> set bflg d0000000
> If your InfoServer has the standard RZ23/24 it should be DKA0 then just
> do a
>>>> b -> with no device after the b
Cannot boot anyway.
The result changed since the InfoServer doesn't stop but tries again and
again to boot from DKA400
>>> SET BOOT DKA400
>>> SET HALT 2
>>> SET BFLG D0000000
>>> BOOT
-DKA400
-DKA400
-DKA400
-DKA400
-DKA400
-DKA400
-DKA400
-DKA400
-DKA400
...
and so on.
I think I have to find the dedicated InfoServer install media...
Thanks
gl
Richard Tomkins
hardware platform was a MicroVAX 3100. As this system was being sold at a
price point below that of a MicroVAX 3100, the firmware was designed to
prevent being able to boot OpenVMS.
In the InfoServer 150, we went a step further and removed the FPU from the
CPU module to reduce the cost. The FPU was never required in any operations
involving the InfoServer design.
The actual OS that the InfoServer ran was custom code that provided LAD/LAST
operations. LAD is Local Area Disk and LAST is Local Area Systems Transport.
LAT, Local Area Transport was also provided for management capability.
The InfoServer actually provided services to Virtual Disks, it was the
Clients responsibility to interpret the served disk.
Disk and Tape functionality was enabled by installing some code from a CD
separate from the actual OS CD.
These units were highly effective in our FIS (Factory Installed Software)
operations in Manufacturing, with some 20 units being able to deliver
OpenVMS, MS-DOS and Windows for a production level of around 200 VAX per
day, 150 Alpha and occasional peeks of 8000 PC's per day. All this in our
Kanata facility.
To make the unit useful, you'll have to find the original CD.
--
Posted via a free Usenet account from http://www.teranews.com
g...@decadence.it
> We designed the InfoServer 100 product to provide disk services. The initial
> hardware platform was a MicroVAX 3100. As this system was being sold at a
> price point below that of a MicroVAX 3100, the firmware was designed to
> prevent being able to boot OpenVMS.
Hello Richard, this is really interesting to me!
I hope I could post and translate to italian this information and put on
my site :)
I suppose the firmware looks at the bootstrap code and only approved
bootstrap is allowed.
I also tried to boot install from Ultrix/VAX 4.5 and NetBSD/VAX 1.6 CDs
and in both cases I was unsuccesful.
So I suppose it isn't VMS that looks at the firmware, but it's really up
to the firmware to look at what is booting.
> The actual OS that the InfoServer ran was custom code that provided LAD/LAST
> operations. LAD is Local Area Disk and LAST is Local Area Systems Transport.
> LAT, Local Area Transport was also provided for management capability.
Is the InfoServer OS a stripped down VMS or rather a totally different
design?
> To make the unit useful, you'll have to find the original CD.
Ouch! :(
Richard Tomkins
As far as figuring out what an OS is looking at, CPUID, SYSTEM ID, memory
structures, it's been so long I cannot remember, but of course the support
in the ROM is minimalist. I seem to recall it went after a hardcoded
filename for booting, but alas, my memory is now failing me so many years
later.
Bob Blunt
If you can find a set of the periodic VMS/OpenVMS CDROM distributions
(CONDIST) one of the CDs usually has a bootable copy of the V3.5A
Infoserver release. IIRC May 1998 VAX CD5 rings a bell... The BFLGs
and other console variables are correct. The Infoserver does not
absolutely require that the bootable device be addressed as DKA0, I've
built many that have used other device addresses besides SCSI ID 6
(which I believe is the initiator's address on desktop VAXen).
As others mentioned, you can't boot VMS/OpenVMS on Infoserver hardware.
Once you get the Infoserver to boot it's O/S everything should be fine
until you lose power unless your system has a good NVRAM backup battery.
If not, reentering the values will be required after power reset.
bob
g...@decadence.it
> If you can find a set of the periodic VMS/OpenVMS CDROM distributions
> (CONDIST) one of the CDs usually has a bootable copy of the V3.5A
> Infoserver release. IIRC May 1998 VAX CD5 rings a bell... The BFLGs
> and other console variables are correct. The Infoserver does not
> absolutely require that the bootable device be addressed as DKA0, I've
> built many that have used other device addresses besides SCSI ID 6
> (which I believe is the initiator's address on desktop VAXen).
>
> As others mentioned, you can't boot VMS/OpenVMS on Infoserver hardware.
> Once you get the Infoserver to boot it's O/S everything should be fine
> until you lose power unless your system has a good NVRAM backup battery.
> If not, reentering the values will be required after power reset.
Hello Bob
unfortunately, I don't have the VAX CONDIST.
I'm looking for the software on bootable CD.
I'm sure I'll find in a way or another.
Bye!
gl
ph...@rephil.org
> unfortunately, I don't have the VAX CONDIST.
> I'm looking for the software on bootable CD.
> I'm sure I'll find in a way or another.
If memory serves, it's on VMS Freeware, either v3, 4, or 5. If not, I
might be able to dig it up.
Cheers,
Phil M
Verne
Once I heard a rumor that with a secret incantation :-) at the
console, any MicroVAX 3100 could successfully boot InfoServer code.
That is, no you cannot turn a real InfoServer into a fully functional
3100, but yes you can turn a fully functional 3100 into an InfoServer
(of course you still must have the proper distribution and install it
onto a hard drive).
With both the InfoServer and the whole 3100 line long out of the sales
channels, does anyone know the >>> commands to make this happen?
Verne
g...@decadence.it
My trouble with InfoServer 100, once again.
I finally managed to get the binary kits for the InfoServer 100 by
downloading them from a FTP site.
I've tried to restore them to the RZ23 disk from InfoServer, but I failed.
Sorry for asking so silly questions to you, I have the hardware but still
not the knowledge to be indipendent.
This is what I did, on another VAX system running VMS 7.3.
$ INITIALIZE DKA100: INFOSERVER
$ BACKUP SYS$SYSROOT:[INFOSERVER.KIT]ESS031.A /SAVE DKA100:[000000]
$ BACKUP SYS$SYSROOT:[INFOSERVER.KIT]F11CD055.A /SAVE DKA100:[000000]
$ BACKUP SYS$SYSROOT:[INFOSERVER.KIT]INFOMO013.A /SAVE DKA100:[000000]
I put back the RZ23 DKA100: into Infoserver, and tried to boot it.
It simply gets into a loop trying to boot from the DKA100:
>>> B DKA100
.
-DKA100
-DKA100
-DKA100
-DKA100
-DKA100
and so on until forever.
I also tried to "INITIALIZE /SYSTEM DKA100:" but I had the same result.
There should be something wrong in the procedure I used, but I really
don't know what.
Any idea?
Thanks a lot!
Bye
gl
Dave Froble
> Hello everybody :)
>
> My trouble with InfoServer 100, once again.
> I finally managed to get the binary kits for the InfoServer 100 by
> downloading them from a FTP site.
>
> I've tried to restore them to the RZ23 disk from InfoServer, but I failed.
> Sorry for asking so silly questions to you, I have the hardware but still
> not the knowledge to be indipendent.
>
> This is what I did, on another VAX system running VMS 7.3.
>
> $ INITIALIZE DKA100: INFOSERVER
> $ BACKUP SYS$SYSROOT:[INFOSERVER.KIT]ESS031.A /SAVE DKA100:[000000]
> $ BACKUP SYS$SYSROOT:[INFOSERVER.KIT]F11CD055.A /SAVE DKA100:[000000]
> $ BACKUP SYS$SYSROOT:[INFOSERVER.KIT]INFOMO013.A /SAVE DKA100:[000000]
I've never run an Infoserver. Regardless, the above is most likely
invalid restoration commands. Instead use (line wraps):
$ BACKUP SYS$SYSROOT:[INFOSERVER.KIT]ESS031.A /SAVE DKA100:[*...]/owner=orig
There may also be an issue with booting. If you would have done an
image backup, AND the save set included the disk initialization data.
A different issue is where you choose to place the [INFOSERVER]
directory. This is opinion, strong opinion, keep non-VMS data out of
the VMS directory structure, namely, SYS$SYSROOT:.
> I put back the RZ23 DKA100: into Infoserver, and tried to boot it.
> It simply gets into a loop trying to boot from the DKA100:
>
>>>> B DKA100
> .
>
> -DKA100
> -DKA100
> -DKA100
> -DKA100
> -DKA100
>
> and so on until forever.
>
> I also tried to "INITIALIZE /SYSTEM DKA100:" but I had the same result.
> There should be something wrong in the procedure I used, but I really
> don't know what.
>
> Any idea?
> Thanks a lot!
>
> Bye
> gl
--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: da...@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486
Peter 'EPLAN' LANGSTOEGER
>My trouble with InfoServer 100, once again.
>I finally managed to get the binary kits for the InfoServer 100 by
>downloading them from a FTP site.
Where? I'm still not aware of binary kits for the InfoServer software.
>I've tried to restore them to the RZ23 disk from InfoServer, but I failed.
>Sorry for asking so silly questions to you, I have the hardware but still
>not the knowledge to be indipendent.
Then you're on the right street here, pal ;-)
>This is what I did, on another VAX system running VMS 7.3.
>
>$ INITIALIZE DKA100: INFOSERVER
>$ BACKUP SYS$SYSROOT:[INFOSERVER.KIT]ESS031.A /SAVE DKA100:[000000]
>$ BACKUP SYS$SYSROOT:[INFOSERVER.KIT]F11CD055.A /SAVE DKA100:[000000]
>$ BACKUP SYS$SYSROOT:[INFOSERVER.KIT]INFOMO013.A /SAVE DKA100:[000000]
What should this do? You try to put the contents of an old InfoServer
Client (!) for OpenVMS (ESS031, was a LAST/DAST add on package for older
VMS versions, V5 IIRC, later VMS versions had then the LAST/DAST protocol
support native) and an old ISO9660 Support AddOn Package for OpenVMS
(V5 IIRC, later versions had ISO9660 Support native in VMS) and another
software for OpenVMS (to obviously monitor an InfoServer) on a disk
destined for the infoserver to boot? This can't work, of course...
And such .A backup savesets are VMSINSTAL kits. For VMS. Got it?
>I put back the RZ23 DKA100: into Infoserver, and tried to boot it.
>It simply gets into a loop trying to boot from the DKA100:
Yes, of course. And the Infoserver is also not running VMS.
And you also made no bootblock on the disk (this would require a
eg. $ BACKUP/IMAGE or eg. $ BACKUP/PHYSICAL or eg. $ MCR WRITEBOOT or...)
>I also tried to "INITIALIZE /SYSTEM DKA100:" but I had the same result.
>There should be something wrong in the procedure I used, but I really
>don't know what.
Why not reading VMS HELP what INIT/SYSTEM does? (Surely not a bootblock).
Have you seen the VMS FAQ already (though I don't know if it would help
with the infoserver, but surely with the things you did or tried to do).
Boot the infoserver from the InfoServer CD (that's the hard part, as I
don't know anyone who still has a copy left), then install the software
onto the infoserver harddisk (but I don't remember how = ~16 years ago)...
(Maybe you can find someone with a working infoserver which duplicates
you its boot disk - BACKUP/PHYSICAL might help).
Once the infoserver is running, you could upgrade the InfoServer to the
latest version (IIRC V3.5A) by "UPDATE SYSTEM FROM DKx:" it from a VAX/VMS
Condist CD (IIRC, the InfoServer Software was on CD#5). I don't know
however (and I still doubt it) if you can also install the infoserver
from CD#5 but maybe you're lucky (as I [used to] have such CDs around)
Later you could then upgrade the Infoserver to more features (Tape Support,
CD Buring Support) by "UPDATE FUNCTIONS FROM dkx:" with appropriate CDs
(which seem to be empty if looked at from VMS - maybe I've a /PHYSICAL copy)
--
Peter "EPLAN" LANGSTOEGER
Network and OpenVMS system specialist
E-mail pe...@langstoeger.at
A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist
g...@decadence.it
>>I finally managed to get the binary kits for the InfoServer 100 by
>>downloading them from a FTP site.
>
> Where? I'm still not aware of binary kits for the InfoServer software.
A person from this newsgroup let me download the software kits from his
machine. I thought it could work.
I just tried since this is the only piece of software I have found right
now and I had nothing to loose.
>>I've tried to restore them to the RZ23 disk from InfoServer, but I
>>failed. Sorry for asking so silly questions to you, I have the hardware
>>but still not the knowledge to be indipendent.
>
> Then you're on the right street here, pal ;-)
A step follow another maybe some day I could walk the street by my own :)
> What should this do? You try to put the contents of an old InfoServer
> Client (!) for OpenVMS (ESS031, was a LAST/DAST add on package for older
> VMS versions, V5 IIRC, later VMS versions had then the LAST/DAST
> protocol support native) and an old ISO9660 Support AddOn Package for
> OpenVMS (V5 IIRC, later versions had ISO9660 Support native in VMS) and
> another software for OpenVMS (to obviously monitor an InfoServer) on a
> disk destined for the infoserver to boot? This can't work, of course...
>
> And such .A backup savesets are VMSINSTAL kits. For VMS. Got it?
Thanks, very clear now.
> Yes, of course. And the Infoserver is also not running VMS. And you also
> made no bootblock on the disk (this would require a eg. $ BACKUP/IMAGE
> or eg. $ BACKUP/PHYSICAL or eg. $ MCR WRITEBOOT or...)
>
> Why not reading VMS HELP what INIT/SYSTEM does? (Surely not a
> bootblock). Have you seen the VMS FAQ already (though I don't know if it
> would help with the infoserver, but surely with the things you did or
> tried to do).
A good point.
In fact I've read documentation very fast and I just went trying things as
they come.
Not a good way at all, thanks for let me remember the right way!
> Boot the infoserver from the InfoServer CD (that's the hard part, as I
> don't know anyone who still has a copy left), then install the software
> onto the infoserver harddisk (but I don't remember how = ~16 years
> ago)... (Maybe you can find someone with a working infoserver which
> duplicates you its boot disk - BACKUP/PHYSICAL might help).
>
> Once the infoserver is running, you could upgrade the InfoServer to the
> latest version (IIRC V3.5A) by "UPDATE SYSTEM FROM DKx:" it from a
> VAX/VMS Condist CD (IIRC, the InfoServer Software was on CD#5). I don't
> know however (and I still doubt it) if you can also install the
> infoserver from CD#5 but maybe you're lucky (as I [used to] have such
> CDs around)
>
> Later you could then upgrade the Infoserver to more features (Tape
> Support, CD Buring Support) by "UPDATE FUNCTIONS FROM dkx:" with
> appropriate CDs (which seem to be empty if looked at from VMS - maybe
> I've a /PHYSICAL copy)
Maybe someday I'll find.
By now I have looked for the Infoserver software CD but I didn't find.
Until then, the InfoServer have to go back in the garage.
Thanks
Bye
gl
g...@decadence.it
> I've never run an Infoserver. Regardless, the above is most likely
> invalid restoration commands. Instead use (line wraps):
>
> $ BACKUP SYS$SYSROOT:[INFOSERVER.KIT]ESS031.A /SAVE DKA100:[*...]/owner=orig
>
> There may also be an issue with booting. If you would have done an
> image backup, AND the save set included the disk initialization data.
I've given I try to your example, but it didn't work because all is
client software, as the other message in the thread explained.
> A different issue is where you choose to place the [INFOSERVER]
> directory. This is opinion, strong opinion, keep non-VMS data out of
> the VMS directory structure, namely, SYS$SYSROOT:.
Thanks for the information, I'll pay more attention to where to put files
for storage.
Bye
gl
VAXelate
As it happens, I have an RZ23 system drive from an Infoserver 100 about
to hit the dumpster that MIGHT still be servicable. I'll remove it
from what's left of the the Infoserver (was earlier cannibalized for
parts) on Monday and see if I can find a VAX or Alpha to connect it to
-- then I can try an image BACKUP -- might just be able to make the
saveset available at that point.
We're in the midst of an office move, I'm afraid, and I have quite a
bit on the go just now, but I'll try to get to it to help out. Those
interested - give me a week or so, and then contact me directly:
moore-dot-mc-at-gmail-dot-com
Chris
Richard Tomkins
then checks the disk and then initializes the disk and copies the OS from
the CD to the disk. The unit then gets set to boot from the disk.
If you had the original CD you could probably duplicate it, possibly even
make an ISO 9660 copy to distribute.
A backup /foreign will probably work as I do not believe (old memory) that
the disk was even remotely files-11 compatible. It was, from what I remember
custom, as you created partitions for the data you wanted to serve. The
partitions were made by specifying a size, the data was interpreted by the
client application accessing the Infoserver, that being DOS, VMS, Mac, and
others.\
g...@decadence.it
> As it happens, I have an RZ23 system drive from an Infoserver 100 about
> to hit the dumpster that MIGHT still be servicable. I'll remove it
> from what's left of the the Infoserver (was earlier cannibalized for
> parts) on Monday and see if I can find a VAX or Alpha to connect it to
> -- then I can try an image BACKUP -- might just be able to make the
> saveset available at that point.
I will probably get another backup image from another person from this
group, but if there are problems I will ask you too.
> We're in the midst of an office move, I'm afraid, and I have quite a
> bit on the go just now, but I'll try to get to it to help out. Those
> interested - give me a week or so, and then contact me directly:
ok, I'll keep in mind.
thanks!
gl
g...@decadence.it
> A backup /foreign will probably work as I do not believe (old memory) that
> the disk was even remotely files-11 compatible. It was, from what I remember
> custom, as you created partitions for the data you wanted to serve. The
> partitions were made by specifying a size, the data was interpreted by the
> client application accessing the Infoserver, that being DOS, VMS, Mac, and
> others.\
Hello Richard
I will try again the backup solution for this problem at least another
time.
If it doesn't work, then I will give up and look for the software cd.
Once again, thanks for the information
Bye
gl
Hoff Hoffman
> Il Sun, 23 Jul 2006 06:11:25 -0700, VAXelate ha scritto:
>> As it happens, I have an RZ23 system drive from an Infoserver 100 about
Y'all are aware that current OpenVMS releases have InfoServer server
capabilities integrated, yes? This in addition to the long-standing
MOP/LAD client capabilities. (IIRC, the first release that had this
officially was V8.2-1, but that it was latent in V8.2.)
VAXelate
mount into aq VAX 4105A. Looks like Richard's comments are spot on.
An image backup produces a VERY small saveset with one Files-11 root
[SYSD] and very little in that. Obviously, much more is needed.
Other than a BACKUP/PHYSICAL (OK if you have an RZ23 with no bad clocks
where mine doesn't...) or shipping out the RZ23, not sure how else to
help, sorry.
Chris
tomars...@comcast.net
the condist cd (which is usually #2), but I dont recall the command. Is
it
>>>b/d0000001 cdrom drive on the infoserver or is it
>>>b/d0000000 cdrom drive
neither one works thru.
thanks
Rich Jordan
Can the Infoserver 1000 boot over the network? I know there was a way
to boot and update an IS1000 via MOP from a VMS system, but I don't
know if an IS100 or 150 could.
The only kit I have here is an InfoServer 1000 updater kit. There are
no IS150 or 100 files or information in it at all.
Rich
g...@decadence.it
I have finally been able to install the InfoServer software (server side!)
on my InfoServer 100 and take it back at work.
I managed to do this only by using an InfoServer Software CD.
It seems there is really no other way to do it.
I have tried a few BACKUP images made by friends from this group, but this
procedure failed each time (and how much time!)
Installing the software from CD (when you have one) only takes a few
seconds.
To find an InfoServer Software CD seems to be an impossible mission,
instead.
I have to pubblically thank the anonymous hero which sent me the ISO
images taken from the original software CD set and also thank everybody
who helped me with software, links and hints about the InfoServer.
That's all, thanks everybody! :)
gl
David J. Dachtera
You would be doing the community a large service if you could provide
some info on how to obtain the CD image(s).
--
David J Dachtera
dba DJE Systems
http://www.djesys.com/
Unofficial OpenVMS Marketing Home Page
http://www.djesys.com/vms/market/
Unofficial Affordable OpenVMS Home Page:
http://www.djesys.com/vms/soho/
Unofficial OpenVMS-IA32 Home Page:
http://www.djesys.com/vms/ia32/
Unofficial OpenVMS Hobbyist Support Page:
http://www.djesys.com/vms/support/
Dan Foster
> "g...@decadence.it" wrote:
>>
>> I have to pubblically thank the anonymous hero which sent me the ISO
>> images taken from the original software CD set and also thank everybody
>> who helped me with software, links and hints about the InfoServer.
>
> You would be doing the community a large service if you could provide
> some info on how to obtain the CD image(s).
Potentially at some legal risk to himself, which I imagine he isn't
anxious to entertain.
I'm sure you're aware that the vendor in question has numerous
representatives here; some actively responding, many others not.
I don't have said software, myself, and imagine I might find it nice to
somehow own (preferrably legally), but I can certainly understand the
situation he is in, and the implications of what you are asking of
him... especially in a public forum.
You should also understand that this country has a long history of being
quite litigious... and you never know whom may be made a example of,
so...
I don't think it's fair for you to ask him to break the law, especially
in a public forum. Now, what you do without public knowledge, well,
anyone can't do much about.
-Dan
David J. Dachtera
Stating the obvious is, well, ...
As simple remark like, "e-mail me privately" from him would probably
suffice and not present much of an issue.
YMMV.
David J. Dachtera
Hobbyists routinely exchange such information here, usually in the form,
"contact me off-line".
I don't see the issue.
Dan Foster
>
> Hobbyists routinely exchange such information here, usually in the form,
> "contact me off-line".
Heh, well, yeah, that'd be the ol' wink-and-nod.
In that case... it is best for the 'offering person' to just simply not
offer in public, and instead, for the 'interested party' to just
privately contact, asking.
That way, you understand, any interested lawyers may not have enough of
a case to go after someone on a mere suspicion. (Lawyers are widely
known for fishing expeditions; I have one for a relative whom was
directly involved in one of the biggest cases in the '80s...)
To *offer* information upon contact is legally dangerous. (The original
poster is from Italy? So? HP has an office in Italy, and can easily file
suit there if they really were interested. How do you think the RIAA
went after people in Australia?)
Some companies uses 'moles' whom don't reveal why they're asking in
order to establish probable cause for a search or warrant, too...
that's a favorite Microsoft tactic.
Hence, it is just simply in the original poster's best interest to not
even publically *offer* any information. Now, in private, well... what
can _I_ or anyone (not knowing a thing about it) do about it? Nothing.
-Dan
P.S. IANAL and all that jazz.
g...@decadence.it
> You would be doing the community a large service if you could provide
> some info on how to obtain the CD image(s).
Hello
I can tell you how I did but... contact me privately! :)
About the question "is it legal to own the InfoServer software" I have a
question for everybody tuned here.
Is the server software part of the InfoServer system itself?
I think yes, because without its software it is a piece of iron and
nothing more.
The InfoServer system is a bundle of hardware and software, as for a
printserver: both the InfoServer and the printserver are hardware system
which run an operating system limited to specific tasks; none could run an
operating system other than their own.
Even the InfoServer software could have been stored in firmware (it takes
seconds to load on disk, so it's really small) and in this case I wouldn't
have to worry about searching for it.
So, given that the InfoServer system is a bundle of hardware and software,
I think it is legal to use the system I've got, as it is legal to power it
on and to hook up a terminal to it.
No matter how I have got it, as long it is a legal way, and I didn't steal
the InfoServer (but it has been given to me in trade for an Amiga 2000 :))
I think there is not an hobbyist program for the InfoServer software only
because there is no need for.
Of course I would *NOT* go around the internet and spread this software as
it was freeware!
ciao!
gl
Hoff Hoffman
> You would be doing the community a large service if you could provide
> some info on how to obtain the CD image(s).
In roughly two weeks' time (as the various wheels churn slowly
forward), you'll be able to download many of the InfoServer giblets,
including keys and disk images and all, from the Freeware site and via
the Freeware disks.
I've packaged up the InfoServer 3.5 image, and keys for most
everything, on Freeware V8.0.
johnhre...@yahoo.com
That's great news. This InfoServer owner thanks you and anyone else
responsible for the release of these goodies. Well done!
Rich Jordan
Hoff,
thank you!
thank you!
thank you!
Woohoo!
Rich
g...@decadence.it
> I've packaged up the InfoServer 3.5 image, and keys for most
> everything, on Freeware V8.0.
Very nice!
If I had started my adventure with the InfoServer two weeks later, I could
have saved myself from sleepless nights around the internet in search for
the software... :)
Thank you
Bye
gl
Dave Froble
I for one wish to offer thanks for this. I don't have an Infoserver so
it's nothing personal. However, from the perspective of not having old
software disappear into the dustbin of history, this is a great act.
David J. Dachtera
I'll add my voice in thanks for this. That's SUPER!
Michael Unger
> In roughly two weeks' time (as the various wheels churn slowly
> forward), you'll be able to download many of the InfoServer giblets,
> including keys and disk images and all, from the Freeware site and via
> the Freeware disks.
>
> I've packaged up the InfoServer 3.5 image, and keys for most
> everything, on Freeware V8.0.
Although I don't have an InfoServer 1000/100/150 (and probably never
will) I appreciate making the software publicly available. After all the
last hardware box was manufactured about a decade ago ...
Michael
--
Real names enhance the probability of getting real answers.
My e-mail account at DECUS Munich is no longer valid.
Ian Miller
INFOSERVERs will find this useful. IIRC VMS Manufacturing used
infoservers - I gues the modern version is the infoserver software on a
Itanium VMS system.