|
|
| Author |
Message |
| 25 new of 292 responses total. |
mcnally
|
|
response 131 of 292:
| 
Oct 25 03:28 UTC 1999 |
more specifically, it's a dig at Microsoft Windows, which produces
"Fatal Exception" errors with distressing frequency..
|
gelinas
|
|
response 132 of 292:
|
Oct 25 03:34 UTC 1999 |
But both are neglecting to mention that the text is the 'exit message'
for the conference, much as diy (or is it micros?) says
Boop
when I leave it.
|
gelinas
|
|
response 133 of 292:
|
Oct 25 03:38 UTC 1999 |
It's micros.
|
aruba
|
|
response 134 of 292:
|
Oct 25 13:24 UTC 1999 |
Grex hung up on me at 9:15 this morning. I was able to get right back on.
|
dpc
|
|
response 135 of 292:
|
Oct 25 14:03 UTC 1999 |
Just a few minutes ago I was on a dialin and experienced the now
all too familiar disconnection without any reason.
|
richard
|
|
response 136 of 292:
|
Oct 25 15:25 UTC 1999 |
does grex get a refund for the days or hours ameritech couldnt provide
the ISDN service it was paying for? would seem only fair
|
aruba
|
|
response 137 of 292:
|
Oct 25 17:28 UTC 1999 |
Yes, I believe we are entitled to a refund. Our ISDN lines cost $48.05 each
these days (including taxes and fees), so two days of service should be worth
(2/30)*($48.05) = $3.20. Not sure if they'd pay for both days since we didn't
call them until Friday evening, and they had it fixed within 24 hours of then.
I'll give it a try.
|
jazz
|
|
response 138 of 292:
|
Oct 25 23:09 UTC 1999 |
Ameritech doesn't offer SLAs on those, do they?
|
keesan
|
|
response 139 of 292:
|
Oct 26 00:30 UTC 1999 |
What is a dynamically linked library?
|
aruba
|
|
response 140 of 292:
|
Oct 26 01:20 UTC 1999 |
Re #138: I don't know what an SLA is.
|
drew
|
|
response 141 of 292:
|
Oct 26 01:39 UTC 1999 |
Re #139:
It is a file containing commonly used functions particular to Windows.
Windows aps depend on these files being there rather than have the code
compiled into the main executable. In theory it cuts down on disk space useage
by eliminating the redundancy of storing the same routines once for each
application.
|
gelinas
|
|
response 142 of 292:
|
Oct 26 01:58 UTC 1999 |
Further, you can update those functions by dropping in a new libary, a
new dll.
"SLA" is "service-level agreement", a statement of what you get for what you
pay.
|
albaugh
|
|
response 143 of 292:
|
Oct 26 04:44 UTC 1999 |
SLA is most often discussed in terms of "support", up-time, response,
24/7, the like.
|
aruba
|
|
response 144 of 292:
|
Oct 26 13:22 UTC 1999 |
I don't know if we have a service-level agreement or not.
|
jazz
|
|
response 145 of 292:
|
Oct 26 19:11 UTC 1999 |
Right. Some ISDN providers guarantee a certain amount of "up-time".
I don't think Ameritech does but it's certainly worth a shot - if Ameritech
did offer an SLA, it'd certainly be an entire month's credit GREX would be
getting insteadd of a few days'.
|
keesan
|
|
response 146 of 292:
|
Oct 29 17:39 UTC 1999 |
Does UNIX also have GPFs? Or only Windows?
|
scott
|
|
response 147 of 292:
|
Oct 29 18:23 UTC 1999 |
Unix has "segmentation faults". Same thing, a program tries to access
something that it isn't supposed to.
|
pfv
|
|
response 148 of 292:
|
Oct 29 20:13 UTC 1999 |
Well... hehe - Actually, unix/linux segfaults are probably
easier to track down, since you can't ever be sure the GPF isn't
directly due to the virus they call an OS..
|
mdw
|
|
response 149 of 292:
|
Oct 29 20:26 UTC 1999 |
In unix, depending on the hardware, it's also possible to get an
"illegal instruction", or "bus" signal, or sometimes a "bad argument to
system call" or other interrupt.
|
pfv
|
|
response 150 of 292:
|
Oct 29 21:06 UTC 1999 |
Oy, geezus.. I had something like that "buss error" thing for
awhile.. Damned catchall is as bad as a GPF.. Fixed it, but gad..
It was depressing.
|
mdw
|
|
response 151 of 292:
|
Oct 29 22:27 UTC 1999 |
What SIGBUS means is hardware dependent, but originally (on the pdp-11 &
vax), it meant an attempt to fetch a word on a non-word boundary -- an
"alignment" error. Many modern machines can fetch words on non-aligned
boundaries (usually with a small performance penalty) so this is not as
likely. The i86 can do unaligned fetches. The 68000 and 68010 require
everything except bytes be at even addresses. The 68020 and + can do
aligned data fetches, but still require that the stack & program counter
be even. The sparc and power risc architectures can't do aligned
fetches. Most powerpc implementations can do aligned data fetches (but
would require word aligned stack & instructions.)
In openbsd, apparently, you'd have to do a systemcall that somehow
invalidates the current stack or data segment; perhaps a call to mmap.
|
pfv
|
|
response 152 of 292:
|
Oct 29 23:13 UTC 1999 |
That was precisely the problem, too.. I had some code developed
(apparently) for DOS that relied on data being so & so arrayed..
I was pretty sure it was that, but I was too tired that day to
track it further.. Thankfully, another grexer took the reins and
slammed out a solution..
Sorta' a Terrible-Day & then the Sun-Came-Out, thang..
|
gelinas
|
|
response 153 of 292:
|
Oct 30 00:17 UTC 1999 |
(Marcus, did you sometimes use "aligned" above when you meant "unaligned"?)
|
mdw
|
|
response 154 of 292:
|
Oct 30 03:25 UTC 1999 |
(Probably. Are you studying to be a proof-reader?)
|
gelinas
|
|
response 155 of 292:
|
Oct 30 03:27 UTC 1999 |
(No, it's a curse.)
|
