mschmitt wrote:Does anyone know what the trick is to active the d(bug) lines in the code?

Change "#define DEBUG 0" to "#define DEBUG 1" in the source file of interest.

Very useful information, and points to what looks like another bug in the same routine as before. Also easily fixed (PM'd to you for build and test; many thanks for your help with this).

Looks like deeper analysis will be needed. I don't know when I'll be able to get to this, and the lack of a Windows build/test environment just makes it that much harder. If anybody else wants to give it a go, please do! Otherwise, I'll have another look sometime after tax season.

Hi again Guys, Is there a certain place in the source code I can look to find the cause of this bug?? To recap, the problem is only happening on the windows builds, basically when copying text and then pasting, SS is adding an invisible character that some programs have a hard time dealing with. Fo...

If it's possible to switch between cursor rendering modes on-the-fly anyway, couldn't this be made a preferences setting? That would get rid of the separate software/hardware cursor builds... There is no SDL build that behaves properly in both S and H modes. I am hoping that a solution for this wil...

Do you know what happened to the built-in preferences editor and/or the "Preferences" item in the application menu and why I cannot make it available building from the current source in CVS? No, I haven't been tracking the CVS tree lately. However, I recall seeing something in the sourcef...

It appears that now also colored cursor icons are displayed correctly in this hardware cursor version. That would make a separate software cursor version superfluous. What you're probably seeing is one of the changes I put into the July version. When an application sets a cursor that the SheepShave...

Some applications seem to be able to save files into the Unix "disk", and others not. I've done a few traces, which suggest that the problem might have to do with the lack of support for MakeFSSpec in Basilisk II's extfs. Unfortunately, I only had time to do a few simple experiments, and w...

Not sure if Pointer Mode will be effective with the SS2008 builds. I just don't know how these builds compute cursor position, especially in third party apps. I suspect that what Pointer Mode does is tell the hosted MacOS to draw the cursor in software, which is also what the SS2008(S) builds do. A...

My question is whether I can use the older 2006 Sheepshaver build and manually configure the "software cursor" option? Afraid not. The cursor location fix and support for using a software cursor are both in the base SheepShaver code, rather than in SDL. You'll get neither of these feature...

Betatester wrote:Yes, the emulated OS freezes, not SS really. Though I have to Force Quite SS to get out of the freeze/hang.

In a situation like this, you can invoke an "emergency quit" from SheepShaver by typing a control-escape.

In the earlier days when Gwenolé himself did answer mails regarding crashes in SS, I had mailed him about SS crashing when launching Framemaker 7.0 in SS-windows. He mailed me something about an upcode-error and said that he would fix it in his new release, and he did so. Framemaker SS-windows work...

Here's the equivalent changes for BasiliskII, if someone would like to test them to make sure they work on Tiger too [ ... ] One additional thing that needs to be done to Basilisk is that BasiliskII.icns is missing from src/MacOSX, and 'make BasiliskII_app' won't work properly without it there. I c...

Charles, thanks very much for devising these changes! Thanks also to Ronald for pinging me, as I had overlooked this thread. The changes look good to me, and I confirm that they fix the inability to build SheepShaver on Leopard. (Note that the SheepShaver binary built on Leopard does not launch on T...

I tried it with SimpleText running in Mac OS 8.6 under the latest Mac OS X Intel SheepShaver build. I did not observe the behavior you describe. It behaved exactly as I would expect it to.

FYI, I have been in touch with the author of TheMouse2B, and he has kindly consented to consider it freeware -- you need not feel guilty about using it without paying the shareware fee. He was delighted to hear that something he wrote years ago is still proving useful.

How would I go about building a windows version with vosf? I never give the --disable-vosf parameter to configure when building. I believe that VOSF is the default, so if you are not configuring with --disable-vosf then your Windows version is probably using it. What puzzles me more is the fact tha...

I do not mind the CPU consumption, it does not seem to cause any problems with other processes that run while I use SheepShaver and the current SheepShaver build itself runs beautifully. I feel the same way, even though I use the hardware cursor version. Maybe the hardware cursor version could be b...

As an experiment to confirm the cause of high CPU consumption, I tried building with the VOSF configuration option enabled. (VOSF is video on segfault, a different approach to video refresh.) This caused CPU consumption to go down dramatically, but video performance with frameskip 0 was poor (those ...

There is a huge difference on my Intel iMac in perceived speed, probably mostly or only the speed in drawing on the screen, between the May 14 2006 snapshot by Gwenole (slow) and the March 11 2007 and later builds (snappy). Could that be related to the CPU usage? Indeed. Gwenole revised the video r...

kelvin31415 did most of the programming lately. Maybe he can shed some light on this problem that apparently was introduced after the 2.3 snapshot ( November 2005) by Gwenole. Since then, more people have made changes to the source though, including Gwenole himself. I'll do some profiling and see i...

Excellent! I'm using your build now. 8)

It would be fine if SheepShaver would just gracefully quit with a comprehensible error message on the screen. I've delivered a fix for the hang, so the app now quits gracefully as intended. I have not yet done anything about the error message, which will appear in the console log as before ("E...

About the mouse button swapping issue I wondered if this is a mistake or a intentional choice, for instance in order to keep the possibility for future use of the second mouse button for a contextual menu for the SheepShaver application itself. Someone any ideas about this? Kelvin? It is just a mis...

Kelvin, Ronald, will there be a new build (whether Intel-only or Universal) in the near future solving the swapping of mouse buttons in Basilisk II and SheepShaver? On 1 July I sent that change to the developer who has been delivering my fixes into CVS, but he has not responded yet. Perhaps he is o...