|
midrange.com
Mark must replying to a bunch of emails this morning. ;)
pnelson@xxxxxxxxx
m
Sent by: To
midrange-l-bounce Midrange Systems Technical
s@xxxxxxxxxxxx Discussion
<midrange-l@xxxxxxxxxxxx>
cc
10/24/2005 10:06
AM Subject
RE: Ops Console problem
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
?
--
Paul Nelson
Arbor Solutions, Inc.
708-670-6978 Cell
pnelson@xxxxxxxxxx
-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
From: "Mark Walter" <mwalter@xxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Date: 10/24/2005 09:50AM
Subject: RE: Ops Console problem
The Super Bowl is in Detroit. I sure as sh*t ain't going there. I think
you mean the Pro Bowl.
Mark Walter
Senior Programmer/Analyst
Hainey Business Systems
(717) 718-9601 x7148
mwalter@xxxxxxxxxxx
http://www.hbs-inc.com
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of pnelson@xxxxxxxxxx
Sent: Monday, October 24, 2005 9:35 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Ops Console problem
I can't seem to find anything in the archives on this.
On Friday night, we rebooted our 520 as part of the weekly backup. On
Saturday, we discovered that the Ops Console could not connect into the
system. We decided to disconnect and reconnect. As the disconnect was
taking place, the laptop showed us one of those wonderful Windos error
messages about memory addresses. We clicked OK and tried to reconnect
again.
No luck, so we rebooted the laptop. Still no luck. All we get is the
message that the ops console is trying to connect. Any ideas as to what
got blown up here?
Thanks.
--
Paul Nelson
Arbor Solutions, Inc.
708-670-6978 Cell
pnelson@xxxxxxxxxx
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
ForwardSourceID:NT00030A2E
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs. For
more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
