Megalextoria
Retro computing and gaming, sci-fi books, tv and movies and other geeky stuff.

Today's Messages (on)  | Unanswered Messages (off)

Forum: Atari ST
 Topic: Kidney Failure! Bad News/Good News!
Kidney Failure! Bad News/Good News! [message #385149] Thu, 18 July 2019 02:24
Anonymous
Karma:
Originally posted by: AtariSales

I'm Refusing To Die!I'm Not Going To Let My Kidneys Or AnythingElse Kill
Me! I'm Going To Stay Here Until Christ Returns!I'm Going To Continue To
Support Atari Users & Remain A Thorn In The Side Of Those Opposing Atari
Sales! My Sunday School Teacher Says "All Things Work Together For Those
Who Love The Lord And Are Called To His Purpose"(Amplified Translation)!
There Is A Song In My Church Based On Christian Scripture That We Sing
With Lyrics Like "And Now,Let The Weak Say I am Strong, Let The Poor Say
I am Rich")!So Continue With Your Prayers, I Appreciate It!Please Reply,
Please Answer, Please Reply Irregardless of your answers! Thanx! =-Ben-=

Games/Software, Hardware/Accessories & Books/References!Atari Computers,
8 Bit & ST Lines + Atari 2600/5200/7800, Jaguar & Lynx Games, Consoles &
Hand Helds! FREE Catalogs At BensCatalogs.Atari.org You Can Also Goto
BenSells.Atari.org Or Request Catalogs By E-Mail At BenSells@Atari.org
Specify Atari 8 Bit, ST, 2600/7800, 5200, Jaguar Or Lynx!!!!! Or Request
Catalog Archives In Either .ARC, .ZIP Or .ZOO Formats! Call Ben Anytime,
(503)256-9974!Come For The Sales, Stay For The Service!Sent On My Atari!
Forum: Computer Folklore
 Topic: IBM Midrange today?
Re: IBM Midrange today? [message #385150 is a reply to message #385142] Thu, 18 July 2019 04:08
Charlie Gibbs is currently offline  Charlie Gibbs
Messages: 4333
Registered: January 2012
Karma:
Senior Member
On 2019-07-17, Dan Espen <dan1espen@gmail.com> wrote:

> Peter Flass <peter_flass@yahoo.com> writes:
>
>> <hancock4@bbs.cpcn.com> wrote:
>>
>>> On Tuesday, July 16, 2019 at 9:30:22 PM UTC-4, Peter Flass wrote:
>>>
>>>> There’s a big difference between some programmers on ISPF and 100,000
>>>> transactions per second on CICS (or IMS). This is the same situation vs.
>>>> midrange systems where the transaction rates are much lower. CICS and IMS
>>>> (and more so TPF) are all aimed at achieving maximum performance, at the
>>>> expense of ease of use.
>>>
>>> I also suspect CICS and IMS were created a lot earlier and
>>> despite upgrades over the years, still relate to their old
>>> roots (like Basic Mapping Support).
>>
>> There’s probably that, too. IBM wants pretty good justification or ROI for
>> adding new features, so adding a text-based mapping feature most likely
>> wouldn’t make the cut.
>
> Our developers wrote a few MFS generators.
> I think some of them were toying with MFS bypass.
>
> As I've recounted before, I did my first online application on
> IBM 2260s. When IBM announced the 3270 my boss asked me to
> evaluate the 3270. I recommended against it. The required datastream
> is crap. When I started using ASCII terminals I was impressed at
> the simplicity of the design and high function.

Yes, I was pretty jealous when I saw how simple things were on minis.
Mainframers insisted that async was only fit for low-speed communication -
the Univac 90/30's serial port could only do 2400 bps, as opposed to the
9600 bps you could get with synchronous. Mind you, with modem prices at
$1/bps in those days, not many people sprang for anything over 2400 bps
if you were going outside the building - two and a half grand for a Bell
201 was enough, especially when you added in the cost of the leased line
you needed for it.

BTW it wasn't ASCII vs. EBCDIC, but the synchronous block-mode protocols
that made things complicated. The Univac 90/30 used EBCDIC (its
non-privileged instructions were bit-for-bit identical to those of
the IBM 360/50), but the terminals were ASCII, with their own form
of multi-dropped bisync protocol. The programming interface was a
nightmare - their Integrated Communications Access Method (ICAM) must
have been at least as bad as IBM's TCAM, BTAM, or whatever alphabet
soup they had (I never got a close look at IBM's offerings). As far as
we (the official Vancouver experts) knew, there was only one person in
all of Canada who really understood ICAM, and a couple of times we flew
him out from Montreal to help us set up something out of the ordinary.
One such case was when we were doing a bisync interface to an IBM
System/38. We spent the entire day on the customer site, and by
the end of the day we finally got it working. Afterwards, we unwound
in an empty office, shooting the bull with our Montreal guru. He
carried on a conversation with us while simultaneously scrambling
and unscrambling a Rubik's Cube. That's the sort of mind it took
to understand this stuff.

I had too much experience with Univac's version of CICS, which they
confusingly called IMS. I wound up creating and interpreting the
datastreams myself - in COBOL, no less.

--
/~\ cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ / I'm really at ac.dekanfrus if you read it the right way.
X Top-posted messages will probably be ignored. See RFC1855.
/ \ "Alexa, define 'bugging'."
Re: IBM Midrange today? [message #385161 is a reply to message #385150] Thu, 18 July 2019 10:17
Dan Espen is currently offline  Dan Espen
Messages: 2991
Registered: January 2012
Karma:
Senior Member
Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:

> On 2019-07-17, Dan Espen <dan1espen@gmail.com> wrote:
>
>> Peter Flass <peter_flass@yahoo.com> writes:
>>
>>> <hancock4@bbs.cpcn.com> wrote:
>>>
>>>> On Tuesday, July 16, 2019 at 9:30:22 PM UTC-4, Peter Flass wrote:
>>>>
>>>> > There’s a big difference between some programmers on ISPF and 100,000
>>>> > transactions per second on CICS (or IMS). This is the same situation vs.
>>>> > midrange systems where the transaction rates are much lower. CICS and IMS
>>>> > (and more so TPF) are all aimed at achieving maximum performance, at the
>>>> > expense of ease of use.
>>>>
>>>> I also suspect CICS and IMS were created a lot earlier and
>>>> despite upgrades over the years, still relate to their old
>>>> roots (like Basic Mapping Support).
>>>
>>> There’s probably that, too. IBM wants pretty good justification or ROI for
>>> adding new features, so adding a text-based mapping feature most likely
>>> wouldn’t make the cut.
>>
>> Our developers wrote a few MFS generators.
>> I think some of them were toying with MFS bypass.
>>
>> As I've recounted before, I did my first online application on
>> IBM 2260s. When IBM announced the 3270 my boss asked me to
>> evaluate the 3270. I recommended against it. The required datastream
>> is crap. When I started using ASCII terminals I was impressed at
>> the simplicity of the design and high function.
>
> Yes, I was pretty jealous when I saw how simple things were on minis.
> Mainframers insisted that async was only fit for low-speed communication -
> the Univac 90/30's serial port could only do 2400 bps, as opposed to the
> 9600 bps you could get with synchronous. Mind you, with modem prices at
> $1/bps in those days, not many people sprang for anything over 2400 bps
> if you were going outside the building - two and a half grand for a Bell
> 201 was enough, especially when you added in the cost of the leased line
> you needed for it.
>
> BTW it wasn't ASCII vs. EBCDIC, but the synchronous block-mode protocols
> that made things complicated.

Agree completely.

Actually there were 3270s that ran in ASCII mode.
They preseented special problems when trying to poll them.
I ended up resorting to channel programming to get them to work
as we wanted.

> The Univac 90/30 used EBCDIC (its
> non-privileged instructions were bit-for-bit identical to those of
> the IBM 360/50), but the terminals were ASCII, with their own form
> of multi-dropped bisync protocol. The programming interface was a
> nightmare - their Integrated Communications Access Method (ICAM) must
> have been at least as bad as IBM's TCAM, BTAM, or whatever alphabet
> soup they had (I never got a close look at IBM's offerings). As far as
> we (the official Vancouver experts) knew, there was only one person in
> all of Canada who really understood ICAM, and a couple of times we flew
> him out from Montreal to help us set up something out of the ordinary.
> One such case was when we were doing a bisync interface to an IBM
> System/38. We spent the entire day on the customer site, and by
> the end of the day we finally got it working. Afterwards, we unwound
> in an empty office, shooting the bull with our Montreal guru. He
> carried on a conversation with us while simultaneously scrambling
> and unscrambling a Rubik's Cube. That's the sort of mind it took
> to understand this stuff.

I'm not a Rubiks cube type but I did have a good grasp on BTAM and VTAM.
VTAM is the latest in IBM Communications. When IBM killed off
BTAM we got on a conference call and explained how our BTAM 3780
product could NOT be ported to VTAM. IBM didn't care. I guess their
BTAM guy was retiring.

Also did a number of VTAM interfaces to 3270s. Not pretty.

--
Dan Espen
Re: IBM Midrange today? [message #385162 is a reply to message #385161] Thu, 18 July 2019 10:44
scott is currently offline  scott
Messages: 3298
Registered: February 2012
Karma:
Senior Member
Dan Espen <dan1espen@gmail.com> writes:
> Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
>
>> On 2019-07-17, Dan Espen <dan1espen@gmail.com> wrote:
>>
>>> Peter Flass <peter_flass@yahoo.com> writes:
>>>

>>
>> BTW it wasn't ASCII vs. EBCDIC, but the synchronous block-mode protocols
>> that made things complicated.
>
> Agree completely.
>
> Actually there were 3270s that ran in ASCII mode.
> They preseented special problems when trying to poll them.
> I ended up resorting to channel programming to get them to work
> as we wanted.

It sounds like IBM datacomm really sucked.

While Burroughs also used EBCDIC, poll/select and block-mode terminals,
no application needed to care - the MCP and the DCP (Data
Comm Processor hardware box) did all the heavy lifting,
including all protocol handling (e.g. POLL/SELECT on
multidrop current-loop or RS232 lines).

All the application needed to care about was the terminal
type (screen vs. hardcopy). The screen control sequences
were the same for over five generations of terminals (TD7x0,
TD8x0, MT983, ET1100, T27) covering twenty five years through
1990.

Moreover, the terminals were common across all the mainframe
lines (small systems, e.g. B1900, medium systems, e.g. B4900,
and large systems, e.g. B6900).

Customers would configure their network using NDL (Network Definition
Language)which associated terminal line # and poll/select address
with the logical stations. NDL is compiled to 'firmware' which is downloaded
to the DCP[*] at boot or when reconfigured.

Then the customer would create an "MCS" using a special descriptive
language to describe the stations and applications; this descriptive
language is used to automatically generate the source code for a BPL program which
interfaces to between one and ten DCP's and routes packets between stations
and applications.

[*] B774 (70's), B874 (70's/80's), B974 (80's, 90's), CP3680 (originally
developed by customer - based on an HP2000 internally and connected to the
host using a mag tape channel controller).
Forum: Anime Misc.
 Topic: Fwd: [New post] Very very bad news…. Tokyo (CNN)At least 23 people are feared dead and 36 injured in a suspected arson attack
Fwd: [New post] Very very bad news…. Tokyo (CNN)At least 23 people are feared dead and 36 injured in a suspected arson attack [message #385155] Thu, 18 July 2019 10:18
Anonymous
Karma:
Originally posted by: Bobbie Sellers

Very Veru bad news indeed,

bliss

-------- Forwarded Message --------
Subject: [New post] vary VARY bad news…. Tokyo (CNN)At least 23 people
are feared dead and 36 injured in a suspected arson attack
Date: Thu, 18 Jul 2019 10:54:56 +0000
From: WordPress.com <donotreply@wordpress.com>



Post : vary VARY bad news&#8230;. Tokyo (CNN)At least 23 people are
feared dead and 36 injured in a suspected arson attack
URL :
< http://www.live-evil.org/archives/2019/07/18/vary-vary-bad-n ews-tokyo-cnnat-least-23-people-are-feared-dead-and-36-injur ed-in-a-suspected-arson-attack>
Posted : Thursday, July 18, 2019 at 11:54 am
Author : suzaku

anime studio burned. I'm at a complete loss of words for this this is a
senseless tragedy.

Read more of this post (
http://www.live-evil.org/archives/2019/07/18/vary-vary-bad-n ews-tokyo-cnnat-least-23-people-are-feared-dead-and-36-injur ed-in-a-suspected-arson-attack
)

Add a comment to this post:
http://www.live-evil.org/archives/2019/07/18/vary-vary-bad-n ews-tokyo-cnnat-least-23-people-are-feared-dead-and-36-injur ed-in-a-suspected-arson-attack#respond

--
 Topic: Kyoani is in fire
Kyoani is in fire [message #385146] Thu, 18 July 2019 00:30
Manbow Papa is currently offline  Manbow Papa
Messages: 95
Registered: March 2012
Karma:
Member
A studio of Kyoto Animation is still burning. A report said that more
than 30 staffs got injured. About 10 of them are in a coma and a few
of them seem to have died. A man of 40+ was caught and is under
investigation by the police. He seems to have spreaded oil on the
floor and fired that caused a huge explosion in the building.

--
/ Ishikawa Kazuo /
Re: Kyoani is in fire [message #385153 is a reply to message #385146] Thu, 18 July 2019 08:32
Dave Baranyi is currently offline  Dave Baranyi
Messages: 976
Registered: January 2012
Karma:
Senior Member
On Thursday, 18 July 2019 00:30:57 UTC-4, Manbow Papa wrote:
> A studio of Kyoto Animation is still burning. A report said that more
> than 30 staffs got injured. About 10 of them are in a coma and a few
> of them seem to have died. A man of 40+ was caught and is under
> investigation by the police. He seems to have spreaded oil on the
> floor and fired that caused a huge explosion in the building.
>
> --
> / Ishikawa Kazuo /

A horrible tragedy. News coverage is now saying that at least 20 people were killed and many more badly burned.

Dave Baranyi
Re: Kyoani is in fire [message #385163 is a reply to message #385153] Thu, 18 July 2019 12:22
Starcade is currently offline  Starcade
Messages: 127
Registered: January 2012
Karma:
Senior Member
Cannot, in any way, be materially surprised.

Current count is 33.

Mike
Forum: Apple II
 Topic: ProDOS port request
Re: ProDOS port request [message #385148 is a reply to message #380007] Thu, 18 July 2019 01:23
Anonymous
Karma:
Originally posted by: Frank M.

Xevious would be a good one.
 Topic: ProDOS port announce
Re: ProDOS port announce [message #385147 is a reply to message #385030] Thu, 18 July 2019 01:21
Anonymous
Karma:
Originally posted by: Frank M.

was the only difference on the 128k zaxxon the double-hires splash screen and switchable mockingboard? not sure it was a legit release.

Looks like BC's got updated to support the ][+ as well...
Re: ProDOS port announce [message #385154 is a reply to message #385147] Thu, 18 July 2019 09:54
qkumba is currently offline  qkumba
Messages: 1009
Registered: March 2013
Karma:
Senior Member
> was the only difference on the 128k zaxxon the double-hires splash screen and switchable mockingboard? not sure it was a legit release.

It seems so. There's a 64kb Mockingboard version, so the 128kb version might be based on that, with the addition of the screen.

> Looks like BC's got updated to support the ][+ as well...

Yes, finally I have finished replacing all of my old 65C02 ports with 6502 versions.
Re: ProDOS port announce [message #385164 is a reply to message #385154] Thu, 18 July 2019 12:48
Antoine Vignau is currently offline  Antoine Vignau
Messages: 1641
Registered: October 2012
Karma:
Senior Member
Zaxxon dhgr was an official release and included in the hgr version.

When I cracked it in late '80s, it was a complete surprize to see the dhgr title screen. I don't remember the details but I think it was visible only on the //c or //e,

Antoine
 Topic: Micro Drive/turbo let’s talk DMA.
Re: Micro Drive/turbo let’s talk DMA. [message #385151 is a reply to message #385143] Thu, 18 July 2019 06:21
Alex Lee is currently offline  Alex Lee
Messages: 180
Registered: November 2012
Karma:
Senior Member
On 2019-07-18 01:09:17 +0000, Leon Sargent said:

> Rom 1 GS
> GSLabs 8 meg card
> VidHD
>
> Micro Drive/Turbo setup app set DMA to Rom 1.
>
> Ciderpressed new image from Whatisthe2gs. Onto CF card.
>
> Booting hangs right before starting the Finder.
>
> Shift booting and it hangs in the finder before the drive icon are drawn
>
> Booting is as slow as before I had a DMA compatible memory card
>
> ——————————————————
>
> Replace image with same from a fresh copy.
>
> DMA disabled
>
> Boot to Finder desktop - no issues
>
> Shift boot into Finder desktop - no issues
>
> Booting is now much faster with DMA set to Disable.
>
> It should be faster with DMA ENABLED and slower with DMA DISABLED but
> this is not the case.
>
> Any help? Thoughts?
>
> Leon

In the MDT utility software, have you specified ROM01 or ROM3? I found
that was critical. If there's an auto setting, it doesn't seem to be
good enough – choose ROM01 or 3.

Alex
Re: Micro Drive/turbo let’s talk DMA. [message #385152 is a reply to message #385151] Thu, 18 July 2019 07:52
Anonymous
Karma:
Originally posted by: Leon Sargent

The DMA is set to ROM 01.

I have been having this issue for a few months.

I formatted the card fat 16. Using Win 10. Not using quick format.

Used MDT utilities to set up the partitions, verified DMA set to ROM 01 and wrote out the configuration.

Only when MDT DMA setting are disabled does the MDT not hang and the computer runs.

Leon
Re: Micro Drive/turbo let’s talk DMA. [message #385165 is a reply to message #385152] Thu, 18 July 2019 13:03
Anonymous
Karma:
Originally posted by: MG

On Thursday, July 18, 2019 at 4:52:50 AM UTC-7, Leon Sargent wrote:
> The DMA is set to ROM 01.
>
> I have been having this issue for a few months.
>
> I formatted the card fat 16. Using Win 10. Not using quick format.
>
> Used MDT utilities to set up the partitions, verified DMA set to ROM 01 and wrote out the configuration.
>
> Only when MDT DMA setting are disabled does the MDT not hang and the computer runs.
>
> Leon

There is a conflict between the VidHD and MDT's DMA that causes the hangs.

As far as I know there is no fix other than to disable DMA on the MDT.

MG
Re: Micro Drive/turbo let’s talk DMA. [message #385166 is a reply to message #385165] Thu, 18 July 2019 13:38
Anonymous
Karma:
Originally posted by: Leon Sargent

The things one forgets to mention. I do have issues with video and the MDT when DMA is on.

So your explanation fits my problem.

Thank you..

Leon



Current Time: Thu Jul 18 15:21:53 EDT 2019

Total time taken to generate the page: 0.01404 seconds