Borland C++ 4.5
Andrew Neil Ramage
nrsc16850 at blueyonder.co.uk
Tue May 31 18:06:42 CDT 2005
The screen was corrupted - the install was a small window in the corner
(ie, it took over the shell window), but when it tried to create a
desktop icon (I think) the whole screen became a patchwork of colours.
You can be the captain
I will draw the chart
Sailing into destiny
Closer to the heart
Closer to the Heart by Rush (A Farewell to Kings, 1977)
wino at piments.com wrote:
> I had a similar situation installing Dragon Nat. Speaking with
> installshield. I thought the thing was hanging and infact it was
> popping up a modal dlg with a yes/no or whatever and wine was failing
> to bring it to the front.
> If the BC installer is hogging the whole screen and you are getting a
> similar disfunction in wine you may think it is hung when it is not.
> There is a line in .wine/config that allows you to catch badly behaved
> installers in 600x800 window so that you can still access the rest of
> the system.
> It's fairly unlikely that an installer will really cripple your kernel
> to the point where you have to power-off.
> On Tue, 31 May 2005 21:53:19 +0200, Kuba Ober <kuba at mareimbrium.org> wrote:
>> On Tuesday 31 May 2005 11:29, Andrew Neil Ramage wrote:
>>> This was a BC++ 4.5 CD I bought years ago. The system I use is SusE 9.2
>>> Desktop (hoping to upgrade to Pro soon) and the latest wine cvs. There
>>> was no debugging information available as the system hung, so I could
>>> not access the shell window I started the install from.
>> Did you try ssh'ing into the system and executing 'killall X' as
>> root? The
>> mere fact that X doesn't react to keystrokes doesn't necessarily mean
>> the system is hanging.
>> Cheers, Kuba
More information about the wine-devel