(sort of) hidden feature in AmigaDOS i found!

[benJamin]

On my machine (A1200/030, OS3.0, blah, blah...), I find the easiest way to reproduce such race-conditions :-o (by which I mean, I learnt to work around it), is to run PPaint, then run Cinema4D.  Cinema will try to open a window while PPaint opens its screen almost every time, hanging the machine.

The other annoying one is OctaMED SS (every version I've had).  It hangs when it tries to open its welcome requester if anything more than the initial 3 windows (Main, Info and Tracker) are set to be open (snapshot windows, leave them open and save the config.) :-x

Patch?  What patch?  I'd /really/ like to upgrade, but my budget says no (woe is me, violins, etc. :-( ) and these niggles are more than a little niggly (sometimes I forget, or am in a hurry, or I'll be opening drawers to run some other program just when PPaint /finally/ decides to show itself:  *Frustration CENTRAL*.


benJamin


"If there is no spoon, how do I eat breakfast?"

[benJamin]

Hmmm... what's mark-up doing to me?  Its my software, don't tell me... :-(


OctaMED SS

The only problem I have is that the white bar across the centre of the tracker window sometimes scrolls up with the notes if I open a window whilst its playing.
- Karlos

So, is that any particular window(s)?  I have, as yet, been unable to replicate it.  Are you useing a graphics card, FastIPrefs?  Is said window not on a 16-pixel boundary, or summat?


I should also recall for you that certain window setups tended not to crash.  I think it was just when I got carried away, as I shall explain.  Yawn

I have a nice, big, hardware-scrolling, rack-like display not at all like Reason:
· Main, Tracker, Info Screen
· Structure windows and some settings (Mix)
· Sample editing Screen (has anyone made any synth automations?)
· Notation/Cluttered Screen (If not notation, then whatever window that I want to keep open in a session.)

I think it's something to do with the time it takes SS to read the keyboard settings file while all the windows are opening; after the file is loaded, the welcome requester is instantiated.  If all the windows take longer than the config file to open, the requester only gets as far as clearing the window zone before hanging with no visible pointer or response (barring a certain salute... ;-) )

My guess would be Chip RAM allocation conflict between the most recent window, and the new, presumably higher priority requester window; though, I'm no sure I've ever been right...

I would like to comfortably be able to save the config at the end of every session, without having to boot with no startup (and thus, no env:), load the config and close some windows and save it if said combo turns out to be a dud combo.  (Or maybe just Save As... config and load everytime, but still, extra, and unnessary steps...  :-( )


Somebody stop me if this should be another thread by now...


benJamin

"On a good day, I'll keep my mouth shut."



PS: Where is the teary-eyed smiley?  :÷(