basilisk-devel — Basilisk II development-related discussion

Re: [B2-devel] [PATCH] Patch for copying and pasting styled text in Basilisk II / SheepShaver

[Charles S. <bas...@ch...>]

On Jun 30, 2012, at 9:27 PM, Alexei Svitkine wrote:

> Thanks. I've landed this now (after cleaning up some of the code formatting).
> 
> I've split this into two commits, the first one renaming the file to have the .mm extension:
> 
> https://github.com/cebix/macemu/commit/3fc0e4dd98c69c39240d061513acddd7dadbc18b
> 
> And the second one containing your code changes:
> 
> https://github.com/cebix/macemu/commit/ed28705ee3c2ff1c382b62d638b20b7fd96e85cd
> 
> Thanks again!
> 
> -Alexei

Thanks. I guess one thing that should still probably be done is to make a parser for utxt/ustl in addition to TEXT/styl. Does anyone know of any Classic apps that write those types on the clipboard (I don’t want to do it without being able to test it)?

If you have an app that you think might write those types but you’re not sure, a good way to test is to copy something to the clipboard, then go into ResEdit, create a new document, and paste. ResEdit turns clipboard flavors into resource types.

Charles

Re: [B2-devel] [PATCH] Patch for copying and pasting styled text in Basilisk II / SheepShaver

[Alexei S. <ale...@gm...>]

Thanks. I've landed this now (after cleaning up some of the code
formatting).

I've split this into two commits, the first one renaming the file to have
the .mm extension:

https://github.com/cebix/macemu/commit/3fc0e4dd98c69c39240d061513acddd7dadbc18b

And the second one containing your code changes:

https://github.com/cebix/macemu/commit/ed28705ee3c2ff1c382b62d638b20b7fd96e85cd

Thanks again!

-Alexei

On Sat, Jun 30, 2012 at 5:50 PM, Charles Srstka <
bas...@ch...> wrote:

> On Jun 30, 2012, at 3:00 PM, Alexei Svitkine wrote:
>
> > At a quick glance the changes look good.
> >
> > Do you mind fixing up the style so its consistent throughout? (i.e.
> making sure indentation is consistent and adding a space after the "if" in
> if statements - right now some have it and others don't.)
> >
> > Then, we can land it in the upstream repository.
> >
> > -Alexei
>
> I just talked to Ronald after sending him a SheepShaver build made from
> applying the patch directly to the source from github, and he says it’s
> working properly on his machine now, so here’s the revised patch:
>
>
>
>
> Thanks,
> Charles
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>
>

Re: [B2-devel] Various issues SheepShaver OSX

[Alexei S. <ale...@gm...>]

On Sat, Jun 30, 2012 at 7:26 PM, Ronald P. Regensburg <ron...@xs...>wrote:

> It took me a while to get (somewhat) familiar with the new GitHub
> repository. But I found where the problem with CD-ROMs not mounting in
> SheepShaver MacOSX started.
>

Thanks for looking into this. That commit was indeed incorrect - I've
reverted it.

-Alexei

Re: [B2-devel] Various issues SheepShaver OSX

[Ronald P. R. <ron...@xs...>]

It took me a while to get (somewhat) familiar with the new GitHub repository. But I found where the problem with CD-ROMs not mounting in SheepShaver MacOSX started.

It started April 21, 2012 with commit
6ee2964818c58fd6d7c512d9f61d2a9d343ebf20
"Fix inverted check from my previous commit."

The commit immediately before that:
2b348f7c4158022d8747ba7fe22c93197d6a059b
"Don't start the Darwin media_thread if "nocdrom" pref is set."
Mounts CD-ROMs alright.

Not sure, but I suppose the "fix" was made by mistake because of the description
"Don't start the Darwin media_thread if "nocdrom" pref is set."
It could better have been described:
Start the Darwin media_thread only if "nocdrom" pref is not set.

;-)

Ronald.


Op 29 jun. 2012, om 02:06 heeft Robert Munafo het volgende geschreven:

> On 6/28/12, Ronald P. Regensburg <ron...@xs...> wrote:
>> An important issue is that SheepShaver OSX appears to have lost the ability
>> to mount CD-ROMs sometime in the past few months.
> 
> The only change we made in the past few months was to fix a bug with
> ejecting: If you have "nocdrom true" in your .sheepshaver_prefs file,
> then it grabbed onto the CD-ROM anyway (even though it made no attempt
> to notify the guest OS that the media was present) and so when you
> tried to eject the CD-ROM, the host (Mac OS X) would refuse to eject
> it. I discovered the fix on April 14th, and notified the other
> developers on the 21st. It was added to CVS on April 21st or 22nd.
> 
> Sheepshaver still mounts CD-ROMs just fine, at least it does for me,
> provided you have "cdrom /dev/poll/cdrom" and "nocdrom false" in your
> .sheepshaver_prefs (and no other lines containing "cdrom"). Example:
> CodeWarrior Pro version 3 MacOS Tools (the CD-ROM containing the
> CodeWarrior IDE, headers and libraries). Not only does it mount, but I
> can repeatedly unmount (by dragging to the trash in the guest OS) and
> re-mount the CD-ROM (by re-inserting it), and the CD-ROM shows up on
> the desktop in the host OS's Finder as well. Furthermore, this
> functionality works equally well in an older SheepShaver from November
> 2010.
> 
> -- 
>  Robert Munafo  --  mrob.com
>  Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 -
> mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com
> 
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
basilisk-devel mailing list
bas...@li...
https://lists.sourceforge.net/lists/listinfo/basilisk-devel

Re: [B2-devel] [PATCH] Patch for copying and pasting styled text in Basilisk II / SheepShaver

[Charles S. <bas...@ch...>]

On Jun 30, 2012, at 3:00 PM, Alexei Svitkine wrote:

> At a quick glance the changes look good.
> 
> Do you mind fixing up the style so its consistent throughout? (i.e. making sure indentation is consistent and adding a space after the "if" in if statements - right now some have it and others don't.)
> 
> Then, we can land it in the upstream repository.
> 
> -Alexei

I just talked to Ronald after sending him a SheepShaver build made from applying the patch directly to the source from github, and he says it’s working properly on his machine now, so here’s the revised patch:

Re: [B2-devel] [PATCH] Patch for copying and pasting styled text in Basilisk II / SheepShaver

[Ronald P. R. <ron...@xs...>]

This (attached) is what Howard sent me.

Ronald.


Op 30 jun. 2012, om 22:05 heeft Charles Srstka het volgende geschreven:

> On Jun 30, 2012, at 3:03 PM, Ronald P. Regensburg wrote:
> 
>> Core 2 Duo iMac, 10.7.4 (64-bit Kernel and Extensions), SheepShaver with your patch running in 64-bit mode:
>> 
>> SimpleText (SheepShaver) -> TextEdit (host)
>> Only plain text arrives (with incorrect accented characters)
>> 
>> TextEdit (host) -> SimpleText (SheepShaver)
>> Only plain text arrives (with correct accented characters)
>> 
>> Tex-Edit Plus 3.0.2 (SheepShaver) -> TextEdit (host)
>> Only plain text arrives (with incorrect accented characters)
>> 
>> TextEdit(host) -> Tex-Edit Plus 3.0.2 (SheepShaver)
>> Only plain text arrives (with correct accented characters)
>> 
>> 
>> I repeated with a previous (June 22, 2012) SheepShaver build, also in 64-bit mode, and the results are exactly the same.
>> 
>> I see no difference at all between the two builds with regard to copying styled text.
>> 
>> Could Howard have applied the patch incorrectly?
> 
> Could be that it’s still running the old clipboard code. Would you mind sending it to me so I could look it over?
> 
> Thanks,
> Charles

Re: [B2-devel] [PATCH] Patch for copying and pasting styled text in Basilisk II / SheepShaver

[Charles S. <bas...@ch...>]

On Jun 30, 2012, at 3:00 PM, Alexei Svitkine wrote:

> At a quick glance the changes look good.
> 
> Do you mind fixing up the style so its consistent throughout? (i.e. making sure indentation is consistent and adding a space after the "if" in if statements - right now some have it and others don't.)
> 
> Then, we can land it in the upstream repository.
> 
> -Alexei

Ah, sorry about that! I noticed that the existing code didn’t use a space before the parens for function calls, and I used the same style for the if statements. Also, Xcode’s automatic indentation likes to use spaces, whereas I see that the existing code was using tabs. I’ve fixed all this.

I think I’ll hold off on sending the revised patch until I hear back from Ronald and see if I can find out what’s causing what he’s seeing.

Charles

Re: [B2-devel] [PATCH] Patch for copying and pasting styled text in Basilisk II / SheepShaver

[Charles S. <bas...@ch...>]

On Jun 30, 2012, at 3:03 PM, Ronald P. Regensburg wrote:

> Core 2 Duo iMac, 10.7.4 (64-bit Kernel and Extensions), SheepShaver with your patch running in 64-bit mode:
> 
> SimpleText (SheepShaver) -> TextEdit (host)
> Only plain text arrives (with incorrect accented characters)
> 
> TextEdit (host) -> SimpleText (SheepShaver)
> Only plain text arrives (with correct accented characters)
> 
> Tex-Edit Plus 3.0.2 (SheepShaver) -> TextEdit (host)
> Only plain text arrives (with incorrect accented characters)
> 
> TextEdit(host) -> Tex-Edit Plus 3.0.2 (SheepShaver)
> Only plain text arrives (with correct accented characters)
> 
> 
> I repeated with a previous (June 22, 2012) SheepShaver build, also in 64-bit mode, and the results are exactly the same.
> 
> I see no difference at all between the two builds with regard to copying styled text.
> 
> Could Howard have applied the patch incorrectly?

Could be that it’s still running the old clipboard code. Would you mind sending it to me so I could look it over?

Thanks,
Charles

Re: [B2-devel] [PATCH] Patch for copying and pasting styled text in Basilisk II / SheepShaver

[Ronald P. R. <ron...@xs...>]

Core 2 Duo iMac, 10.7.4 (64-bit Kernel and Extensions), SheepShaver with your patch running in 64-bit mode:

SimpleText (SheepShaver) -> TextEdit (host)
Only plain text arrives (with incorrect accented characters)

TextEdit (host) -> SimpleText (SheepShaver)
Only plain text arrives (with correct accented characters)

Tex-Edit Plus 3.0.2 (SheepShaver) -> TextEdit (host)
Only plain text arrives (with incorrect accented characters)

TextEdit(host) -> Tex-Edit Plus 3.0.2 (SheepShaver)
Only plain text arrives (with correct accented characters)


I repeated with a previous (June 22, 2012) SheepShaver build, also in 64-bit mode, and the results are exactly the same.

I see no difference at all between the two builds with regard to copying styled text.

Could Howard have applied the patch incorrectly?

Ronald.


Op 30 jun. 2012, om 21:08 heeft Charles Srstka het volgende geschreven:

> I don’t have a version of AppleWorks that works in Classic, and I haven’t been able to get Word to start up in SheepShaver, but I’ve tried the following combinations, and all seem to work:
> 
> SimpleText (SheepShaver) -> TextEdit (host)
> TextEdit (host) -> SimpleText (SheepShaver)
> Tex-Edit 4.1.3 (SheepShaver) -> TextEdit (host)
> TextEdit(host) -> Tex-Edit 4.1.3 (SheepShaver)
> 
> All seem to work on my machine (MBP, 10.7.4, 64-bit).
> 
> One thing to note is that all the changes I made went into the 64-bit clipboard code. This is because I anticipate that this code will probably end up eventually replacing the 32-bit code outright, so there’s no real point in working on the 32-bit code. Make sure you’re running in 64-bit mode.
> 
> If it’s still not working for you, would it be okay to send me your patched version of the code, so that I can see if I accidentally left anything out of the patch?
> 
> Thanks,
> Charles
> 
> On Jun 30, 2012, at 1:53 PM, Ronald P. Regensburg wrote:
> 
>> Howard Spoelstra (Cat_7 in Emaculation) applied your patch to the latest git version and built a SheepShaver.app from it that he sent to me to try.
>> 
>> Maybe copying styled text should work with some specific applications? I could not make it work either way with the applications I tried: From Word and TextEdit in OSX nothing appeared on the MacOS clipboard, from AppleWorks in MacOS nothing appeared on the OSX clipboard and from Tex-Edit Plus in MacOS only plain text appeared on the OSX clipboard.
>> 
>> The problem with accented characters while copying plain text from MacOS to OSX in 64-bit mode is not solved.
>> 
>> (This build also has the earlier reported problem of not being able to mount CD-ROMs.)
>> 
>> (The recent patch that prevents disk images to be mounted in OSX and SheepShaver at the same time seems to work both ways.)
>> 
>> Ronald.
>> 
>> 
>> Op 30 jun. 2012, om 03:22 heeft Charles Srstka het volgende geschreven:
>> 
>>> Added code to parse the Classic Mac OS 'styl' resources, allowing formatted text to be copied and pasted out of SheepShaver, not just plain text. In order to do this, I made some changes to the emul_op mechanism, patching ZeroScrap() in addition to the scrap methods that were already being patched. The reason for this is that since we need to read data from multiple items that are on the clipboard at once, we cannot simply assume a zero at the beginning of each PutScrap() operation.
>>> 
>>> This patch uses RTF to store styled text on the host side; unfortunately, since the APIs to convert to and from RTF data are in Cocoa but not in CoreFoundation, I had to write the new portions in Objective-C rather than C, and changed the extension from .cpp to .mm accordingly. In the future, if we are confident that this file will only be used on Mac OS X 10.6 and up, we can rewrite the Pasteboard Manager code to use NSPasteboardReading/Writing instead. This would allow us to read and write NSAttributedString objects directly to and from the pasteboard, which would make sure we were always using the OS's preferred rich text format internally instead of hard-coding it specifically to RTF as in the current implementation.
>>> 
>>> I believe that this patch should also fix the problem Ronald reported with copying accented characters.
>>> 
>>> Since I am new to 68k assembly and the emul_op mechanism, I would appreciate if someone could double-check all my changes to make sure that I have done everything correctly.
>>> 
>>> Thanks,
>>> Charles
>>> 
> 

Re: [B2-devel] [PATCH] Patch for copying and pasting styled text in Basilisk II / SheepShaver

[Alexei S. <ale...@gm...>]

At a quick glance the changes look good.

Do you mind fixing up the style so its consistent throughout? (i.e. making
sure indentation is consistent and adding a space after the "if" in if
statements - right now some have it and others don't.)

Then, we can land it in the upstream repository.

-Alexei

On Sat, Jun 30, 2012 at 3:08 PM, Charles Srstka <
bas...@ch...> wrote:

> I don’t have a version of AppleWorks that works in Classic, and I haven’t
> been able to get Word to start up in SheepShaver, but I’ve tried the
> following combinations, and all seem to work:
>
> SimpleText (SheepShaver) -> TextEdit (host)
> TextEdit (host) -> SimpleText (SheepShaver)
> Tex-Edit 4.1.3 (SheepShaver) -> TextEdit (host)
> TextEdit(host) -> Tex-Edit 4.1.3 (SheepShaver)
>
> All seem to work on my machine (MBP, 10.7.4, 64-bit).
>
> One thing to note is that all the changes I made went into the 64-bit
> clipboard code. This is because I anticipate that this code will probably
> end up eventually replacing the 32-bit code outright, so there’s no real
> point in working on the 32-bit code. Make sure you’re running in 64-bit
> mode.
>
> If it’s still not working for you, would it be okay to send me your
> patched version of the code, so that I can see if I accidentally left
> anything out of the patch?
>
> Thanks,
> Charles
>
> On Jun 30, 2012, at 1:53 PM, Ronald P. Regensburg wrote:
>
> > Howard Spoelstra (Cat_7 in Emaculation) applied your patch to the latest
> git version and built a SheepShaver.app from it that he sent to me to try.
> >
> > Maybe copying styled text should work with some specific applications? I
> could not make it work either way with the applications I tried: From Word
> and TextEdit in OSX nothing appeared on the MacOS clipboard, from
> AppleWorks in MacOS nothing appeared on the OSX clipboard and from Tex-Edit
> Plus in MacOS only plain text appeared on the OSX clipboard.
> >
> > The problem with accented characters while copying plain text from MacOS
> to OSX in 64-bit mode is not solved.
> >
> > (This build also has the earlier reported problem of not being able to
> mount CD-ROMs.)
> >
> > (The recent patch that prevents disk images to be mounted in OSX and
> SheepShaver at the same time seems to work both ways.)
> >
> > Ronald.
> >
> >
> > Op 30 jun. 2012, om 03:22 heeft Charles Srstka het volgende geschreven:
> >
> >> Added code to parse the Classic Mac OS 'styl' resources, allowing
> formatted text to be copied and pasted out of SheepShaver, not just plain
> text. In order to do this, I made some changes to the emul_op mechanism,
> patching ZeroScrap() in addition to the scrap methods that were already
> being patched. The reason for this is that since we need to read data from
> multiple items that are on the clipboard at once, we cannot simply assume a
> zero at the beginning of each PutScrap() operation.
> >>
> >> This patch uses RTF to store styled text on the host side;
> unfortunately, since the APIs to convert to and from RTF data are in Cocoa
> but not in CoreFoundation, I had to write the new portions in Objective-C
> rather than C, and changed the extension from .cpp to .mm accordingly. In
> the future, if we are confident that this file will only be used on Mac OS
> X 10.6 and up, we can rewrite the Pasteboard Manager code to use
> NSPasteboardReading/Writing instead. This would allow us to read and write
> NSAttributedString objects directly to and from the pasteboard, which would
> make sure we were always using the OS's preferred rich text format
> internally instead of hard-coding it specifically to RTF as in the current
> implementation.
> >>
> >> I believe that this patch should also fix the problem Ronald reported
> with copying accented characters.
> >>
> >> Since I am new to 68k assembly and the emul_op mechanism, I would
> appreciate if someone could double-check all my changes to make sure that I
> have done everything correctly.
> >>
> >> Thanks,
> >> Charles
> >>
> >
> >
> ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > basilisk-devel mailing list
> > bas...@li...
> > https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>

Re: [B2-devel] [PATCH] Patch for copying and pasting styled text in Basilisk II / SheepShaver

[Charles S. <bas...@ch...>]

I don’t have a version of AppleWorks that works in Classic, and I haven’t been able to get Word to start up in SheepShaver, but I’ve tried the following combinations, and all seem to work:

SimpleText (SheepShaver) -> TextEdit (host)
TextEdit (host) -> SimpleText (SheepShaver)
Tex-Edit 4.1.3 (SheepShaver) -> TextEdit (host)
TextEdit(host) -> Tex-Edit 4.1.3 (SheepShaver)

All seem to work on my machine (MBP, 10.7.4, 64-bit).

One thing to note is that all the changes I made went into the 64-bit clipboard code. This is because I anticipate that this code will probably end up eventually replacing the 32-bit code outright, so there’s no real point in working on the 32-bit code. Make sure you’re running in 64-bit mode.

If it’s still not working for you, would it be okay to send me your patched version of the code, so that I can see if I accidentally left anything out of the patch?

Thanks,
Charles

On Jun 30, 2012, at 1:53 PM, Ronald P. Regensburg wrote:

> Howard Spoelstra (Cat_7 in Emaculation) applied your patch to the latest git version and built a SheepShaver.app from it that he sent to me to try.
> 
> Maybe copying styled text should work with some specific applications? I could not make it work either way with the applications I tried: From Word and TextEdit in OSX nothing appeared on the MacOS clipboard, from AppleWorks in MacOS nothing appeared on the OSX clipboard and from Tex-Edit Plus in MacOS only plain text appeared on the OSX clipboard.
> 
> The problem with accented characters while copying plain text from MacOS to OSX in 64-bit mode is not solved.
> 
> (This build also has the earlier reported problem of not being able to mount CD-ROMs.)
> 
> (The recent patch that prevents disk images to be mounted in OSX and SheepShaver at the same time seems to work both ways.)
> 
> Ronald.
> 
> 
> Op 30 jun. 2012, om 03:22 heeft Charles Srstka het volgende geschreven:
> 
>> Added code to parse the Classic Mac OS 'styl' resources, allowing formatted text to be copied and pasted out of SheepShaver, not just plain text. In order to do this, I made some changes to the emul_op mechanism, patching ZeroScrap() in addition to the scrap methods that were already being patched. The reason for this is that since we need to read data from multiple items that are on the clipboard at once, we cannot simply assume a zero at the beginning of each PutScrap() operation.
>> 
>> This patch uses RTF to store styled text on the host side; unfortunately, since the APIs to convert to and from RTF data are in Cocoa but not in CoreFoundation, I had to write the new portions in Objective-C rather than C, and changed the extension from .cpp to .mm accordingly. In the future, if we are confident that this file will only be used on Mac OS X 10.6 and up, we can rewrite the Pasteboard Manager code to use NSPasteboardReading/Writing instead. This would allow us to read and write NSAttributedString objects directly to and from the pasteboard, which would make sure we were always using the OS's preferred rich text format internally instead of hard-coding it specifically to RTF as in the current implementation.
>> 
>> I believe that this patch should also fix the problem Ronald reported with copying accented characters.
>> 
>> Since I am new to 68k assembly and the emul_op mechanism, I would appreciate if someone could double-check all my changes to make sure that I have done everything correctly.
>> 
>> Thanks,
>> Charles
>> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel

Re: [B2-devel] [PATCH] Patch for copying and pasting styled text in Basilisk II / SheepShaver

[Ronald P. R. <ron...@xs...>]

Howard Spoelstra (Cat_7 in Emaculation) applied your patch to the latest git version and built a SheepShaver.app from it that he sent to me to try.

Maybe copying styled text should work with some specific applications? I could not make it work either way with the applications I tried: From Word and TextEdit in OSX nothing appeared on the MacOS clipboard, from AppleWorks in MacOS nothing appeared on the OSX clipboard and from Tex-Edit Plus in MacOS only plain text appeared on the OSX clipboard.

The problem with accented characters while copying plain text from MacOS to OSX in 64-bit mode is not solved.

(This build also has the earlier reported problem of not being able to mount CD-ROMs.)

(The recent patch that prevents disk images to be mounted in OSX and SheepShaver at the same time seems to work both ways.)

Ronald.


Op 30 jun. 2012, om 03:22 heeft Charles Srstka het volgende geschreven:

> Added code to parse the Classic Mac OS 'styl' resources, allowing formatted text to be copied and pasted out of SheepShaver, not just plain text. In order to do this, I made some changes to the emul_op mechanism, patching ZeroScrap() in addition to the scrap methods that were already being patched. The reason for this is that since we need to read data from multiple items that are on the clipboard at once, we cannot simply assume a zero at the beginning of each PutScrap() operation.
> 
> This patch uses RTF to store styled text on the host side; unfortunately, since the APIs to convert to and from RTF data are in Cocoa but not in CoreFoundation, I had to write the new portions in Objective-C rather than C, and changed the extension from .cpp to .mm accordingly. In the future, if we are confident that this file will only be used on Mac OS X 10.6 and up, we can rewrite the Pasteboard Manager code to use NSPasteboardReading/Writing instead. This would allow us to read and write NSAttributedString objects directly to and from the pasteboard, which would make sure we were always using the OS's preferred rich text format internally instead of hard-coding it specifically to RTF as in the current implementation.
> 
> I believe that this patch should also fix the problem Ronald reported with copying accented characters.
> 
> Since I am new to 68k assembly and the emul_op mechanism, I would appreciate if someone could double-check all my changes to make sure that I have done everything correctly.
> 
> Thanks,
> Charles
> 

Re: [B2-devel] Various issues SheepShaver OSX

[Charles S. <bas...@ch...>]

On Jun 30, 2012, at 4:55 AM, Ronald P. Regensburg wrote:

> 
> Op 29 jun. 2012, om 23:49 heeft Robert Munafo het volgende geschreven:
> 
>> On 6/29/12, Ronald P. Regensburg <ron...@xs...> wrote:
>>> Well, strange that you do not have the problem. I tried again and mounting
>>> CD-ROMs is definitely broken here.
>>> 
>>> [...]
>>> 
>>> So what can be different between your setup and mine that could explain why
>>> you do not see the problem and I do?
>> 
>> Here are the differences I notice:
>> 
>> * I'm using Snow Leopard 10.6.8, you're using Lion
> 
> I tried in 10.6.8 and the issue is there also.
> 
> 
>> * I haven't tried building anything off git because I don't know how to (yet)
> 
> Maybe the problems is of very recent date, after the source was moved from CVS to Git?
> 
> I am also still struggling how to use git, but getting the latest revision is easy:
> 
> https://github.com/cebix/macemu
> Click "Downloads", and on the Downloads page click the "Download as zip" button.

Typing this into the Terminal:

git clone https://github.com/cebix/macemu

is better than downloading the zip file, since this makes you a cloned repository with all the invisible “.git” directories. Without that stuff, it is much more of a pain to create patches.

Charles

Re: [B2-devel] Various issues SheepShaver OSX

[Ronald P. R. <ron...@xs...>]

Op 29 jun. 2012, om 23:49 heeft Robert Munafo het volgende geschreven:

> On 6/29/12, Ronald P. Regensburg <ron...@xs...> wrote:
>> Well, strange that you do not have the problem. I tried again and mounting
>> CD-ROMs is definitely broken here.
>> 
>> [...]
>> 
>> So what can be different between your setup and mine that could explain why
>> you do not see the problem and I do?
> 
> Here are the differences I notice:
> 
>  * I'm using Snow Leopard 10.6.8, you're using Lion

I tried in 10.6.8 and the issue is there also.


>  * I haven't tried building anything off git because I don't know how to (yet)

Maybe the problems is of very recent date, after the source was moved from CVS to Git?

I am also still struggling how to use git, but getting the latest revision is easy:

https://github.com/cebix/macemu
Click "Downloads", and on the Downloads page click the "Download as zip" button.


> 
> But I do have the same version of Xcode (i.e. the GCC compiler) and am
> building under Mac OS 10.6.8. Also, our prefs files look good, and we
> agree in that the older versions (March 2012 and earlier) work fine.
> 
> -- 
>  Robert Munafo  --  mrob.com

[B2-devel] [PATCH] Patch for copying and pasting styled text in Basilisk II / SheepShaver

[Charles S. <bas...@ch...>]

Added code to parse the Classic Mac OS 'styl' resources, allowing formatted text to be copied and pasted out of SheepShaver, not just plain text. In order to do this, I made some changes to the emul_op mechanism, patching ZeroScrap() in addition to the scrap methods that were already being patched. The reason for this is that since we need to read data from multiple items that are on the clipboard at once, we cannot simply assume a zero at the beginning of each PutScrap() operation.

This patch uses RTF to store styled text on the host side; unfortunately, since the APIs to convert to and from RTF data are in Cocoa but not in CoreFoundation, I had to write the new portions in Objective-C rather than C, and changed the extension from .cpp to .mm accordingly. In the future, if we are confident that this file will only be used on Mac OS X 10.6 and up, we can rewrite the Pasteboard Manager code to use NSPasteboardReading/Writing instead. This would allow us to read and write NSAttributedString objects directly to and from the pasteboard, which would make sure we were always using the OS's preferred rich text format internally instead of hard-coding it specifically to RTF as in the current implementation.

I believe that this patch should also fix the problem Ronald reported with copying accented characters.

Since I am new to 68k assembly and the emul_op mechanism, I would appreciate if someone could double-check all my changes to make sure that I have done everything correctly.

Thanks,
Charles

Re: [B2-devel] Various issues SheepShaver OSX

[Robert M. <mr...@gm...>]

On 6/29/12, Ronald P. Regensburg <ron...@xs...> wrote:
> Well, strange that you do not have the problem. I tried again and mounting
> CD-ROMs is definitely broken here.
>
>[...]
>
> So what can be different between your setup and mine that could explain why
> you do not see the problem and I do?

Here are the differences I notice:

  * I'm using Snow Leopard 10.6.8, you're using Lion
  * I haven't tried building anything off git because I don't know how to (yet)

But I do have the same version of Xcode (i.e. the GCC compiler) and am
building under Mac OS 10.6.8. Also, our prefs files look good, and we
agree in that the older versions (March 2012 and earlier) work fine.

-- 
  Robert Munafo  --  mrob.com
  Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 -
mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com

Re: [B2-devel] Various issues SheepShaver OSX

[Ronald P. R. <ron...@xs...>]

Well, strange that you do not have the problem. I tried again and mounting CD-ROMs is definitely broken here.

Intel Core 2 Duo iMac, OSX 10.7.4, a CD-ROM mounted in OSX. (This time an ordinary late 90's MacWorld CD with shareware and updates. I tried different CD-ROMs before, among which MacOS install CDs, with identical results.)

Five SheepShaver builds, all five in the same folder and using the same prefs, with MacOS 9.0.4 installed:

1. CVS 2012/02/11
2. CVS 2012/03/28
3. GitHub 2012/06/22
4. GitHub 2012/06/23
5. GitHub 2012/06/28

All five were built using the XCode project, with XCode 3.2.6 in OSX 10.6.8.

When I launch 1 or 2, one can hear the drive reading the CD and the CD appears as expected on the MacOS desktop.

When I launch 3, 4, or 5, the drive remains silent and the CD does not appear on the MacOS desktop.

When I try to first launch and start up SheepShaver and then insert the CD, the CD mounts in both host and guest OS with 1 and 2. With 3, 4, and 5, the CD only mounts in the host OS.

All results are the same regardless whether running these SheepShaver apps in 32-bit mode or in 64-bit mode.


~/.sheepshaver_prefs:

disk MacOSHD.dmg
disk heenenweer+.dmg
cdrom /dev/poll/cdrom
extfs doorgeefluik
screen win/1280/800
windowmodes 0
screenmodes 0
seriala /dev/cu.Bluetooth-Modem
serialb /dev/null
rom Mac OS ROM
bootdrive 0
bootdriver 0
ramsize 536870912
frameskip 1
gfxaccel true
nocdrom false
nonet false
nosound false
nogui true
noclipconversion false
ignoresegv true
jit true
jit68k false
keyboardtype 5
ether slirp
keycodes true
keycodefile keycodes
mousewheelmode 0
mousewheellines 0
dsp /dev/dsp
mixer /dev/mixer
ignoresegv true
idlewait true


So what can be different between your setup and mine that could explain why you do not see the problem and I do?

Ronald.


Op 29 jun. 2012, om 02:06 heeft Robert Munafo het volgende geschreven:

> On 6/28/12, Ronald P. Regensburg <ron...@xs...> wrote:
>> An important issue is that SheepShaver OSX appears to have lost the ability
>> to mount CD-ROMs sometime in the past few months.
> 
> The only change we made in the past few months was to fix a bug with
> ejecting: If you have "nocdrom true" in your .sheepshaver_prefs file,
> then it grabbed onto the CD-ROM anyway (even though it made no attempt
> to notify the guest OS that the media was present) and so when you
> tried to eject the CD-ROM, the host (Mac OS X) would refuse to eject
> it. I discovered the fix on April 14th, and notified the other
> developers on the 21st. It was added to CVS on April 21st or 22nd.
> 
> Sheepshaver still mounts CD-ROMs just fine, at least it does for me,
> provided you have "cdrom /dev/poll/cdrom" and "nocdrom false" in your
> .sheepshaver_prefs (and no other lines containing "cdrom"). Example:
> CodeWarrior Pro version 3 MacOS Tools (the CD-ROM containing the
> CodeWarrior IDE, headers and libraries). Not only does it mount, but I
> can repeatedly unmount (by dragging to the trash in the guest OS) and
> re-mount the CD-ROM (by re-inserting it), and the CD-ROM shows up on
> the desktop in the host OS's Finder as well. Furthermore, this
> functionality works equally well in an older SheepShaver from November
> 2010.
> 
> -- 
>  Robert Munafo  --  mrob.com
>  Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 -
> mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com
> 

Re: [B2-devel] Various issues SheepShaver OSX

[Robert M. <mr...@gm...>]

On 6/28/12, Ronald P. Regensburg <ron...@xs...> wrote:
> An important issue is that SheepShaver OSX appears to have lost the ability
> to mount CD-ROMs sometime in the past few months.

The only change we made in the past few months was to fix a bug with
ejecting: If you have "nocdrom true" in your .sheepshaver_prefs file,
then it grabbed onto the CD-ROM anyway (even though it made no attempt
to notify the guest OS that the media was present) and so when you
tried to eject the CD-ROM, the host (Mac OS X) would refuse to eject
it. I discovered the fix on April 14th, and notified the other
developers on the 21st. It was added to CVS on April 21st or 22nd.

Sheepshaver still mounts CD-ROMs just fine, at least it does for me,
provided you have "cdrom /dev/poll/cdrom" and "nocdrom false" in your
.sheepshaver_prefs (and no other lines containing "cdrom"). Example:
CodeWarrior Pro version 3 MacOS Tools (the CD-ROM containing the
CodeWarrior IDE, headers and libraries). Not only does it mount, but I
can repeatedly unmount (by dragging to the trash in the guest OS) and
re-mount the CD-ROM (by re-inserting it), and the CD-ROM shows up on
the desktop in the host OS's Finder as well. Furthermore, this
functionality works equally well in an older SheepShaver from November
2010.

-- 
  Robert Munafo  --  mrob.com
  Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 -
mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com

Re: [B2-devel] Various issues SheepShaver OSX

[Giulio P. <giu...@gm...>]

Il 28/06/2012 21:47, Ronald P. Regensburg ha scritto:
> 
> Thanks for your answer. But remember that I am only a (experienced) user of SheepShaver and BasiliskII, not a developer.
> I filed issues I encountered as a user with builds created with recent source.
> I do not intend to change anything myself, I would not know how to, I
hope others will solve the problems.

I see.

> "Clone repository"? "Working directory"? What is my working directory? Do I have one?

A "working directory" is the copy of the content of a specific revision
that you have on your computer.

"Clone repository" is how you get your copy starting from a git repository.

> I only want to be able to download the source of certain dates, to build the application from it, so I can see and report when a problem starts.
> That could provide information about where to look for the code that
is responsible.

> With CVS I knew the commands needed to do that, and I did so on several occasions. But I do not know how to do that with GitHub.
> Your instructions presuppose knowledge I do not have and possibly need software on my Mac I do not have installed.

The instructions I gave were about the command line tool.

Given what you said, maybe you want to try the "github for mac": you can
get it at http://mac.github.com/.

Unfortunately I never used it, so I cannot help, but I think that it
should be easy to use.

Remember that "clone" retrieve the whole repository from the net, while
"checkout" allows to move inside the repository to get a specific revision.

> I don't think I want or need the whole repository and history.

To do what you want to do, you want the whole repository (this is how
you get a specific revision with git).

Bests,
	Giulio.


> Op 28 jun. 2012, om 20:09 heeft Giulio Paci het volgende geschreven:
> 
>> On 28/06/2012 19:13, Ronald P. Regensburg wrote:
>>>
>>> I started to file issues with SheepShaver OSX here:
>>>
>>> https://github.com/cebix/macemu/issues
>>>
>>> I hope someone will look into these issues. More will follow.
>>>
>>> An important issue is that SheepShaver OSX appears to have lost the ability to mount CD-ROMs sometime in the past few months. I have no experience with GitHub and I do not know how to narrow the issue down to a specific patch. With CVS I used to download the source from different dates to see where a specific issue appeared. Can that be done here as well? How?
>>
>> 1) When you clone a repository (e.g., git clone
>> https://github.com/cebix/macemu.git) you have the whole history in the
>> .git directory in your working directory.
>>
>> You can get a specific revision with the checkout command (e.g.: git
>> checkout <hash_tag_of_the_revision>). This will change the content of
>> your working directory with those of the desired revision.
>>
>> You can get the revisions history (with hash tags) with the log command.
>> You can see which files have been changed with "git log --raw".
>>
>> You can also compare directly two revisions with the diff command.
>>
>> You can also have a look at the bisect command.
>>
>> Remember that you also can do "git help command" to get help.
>>
>> 2) If you want to change something and not just find the revision that
>> introduced the bug, I suggest to use the fork button on github and clone
>> your repository instead of the main one. This will simplify merging your
>> changes in the main repository later.
>>
>> Bests,
>> 	Giulio.
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel

Re: [B2-devel] Various issues SheepShaver OSX

[Ronald P. R. <ron...@xs...>]

Thanks for your answer. But see my answer to Giulio Paci.

Your tips would probably be useful to developers. It does not help me with what I asked for.

Best,  Ronald.


Op 28 jun. 2012, om 20:56 heeft Alexander von Gluck het volgende geschreven:

> On 28.06.2012 12:13, Ronald P. Regensburg wrote:
>> I started to file issues with SheepShaver OSX here:
>> 
>> https://github.com/cebix/macemu/issues
>> 
>> I hope someone will look into these issues. More will follow.
>> 
>> An important issue is that SheepShaver OSX appears to have lost the 
>> ability to mount CD-ROMs sometime in the past few
>> months. I have no experience with GitHub and I do not know how to narrow 
>> the issue down to a specific patch. With CVS
>> I used to download the source from different dates to see where a specific 
>> issue appeared. Can that be done here as
>> well? How?
> 
> 
> git has a great feature for finding regressions called bisect
> 
> http://webchick.net/node/99
> http://alblue.bandlem.com/2011/07/git-tip-of-week-git-bisect.html
> 
> you provide a known "good" revision, and a known "bad" revision. (you don't 
> *have to provide the good revision...
> however it definitely narrows down the pool of all commits to tree since the 
> beginning of time)
> 
> Git then will start cutting the commits in half to narrow down where the 
> problem started.
> 
>  -- Alex
> 

Re: [B2-devel] Various issues SheepShaver OSX

[Ronald P. R. <ron...@xs...>]

Thanks for your answer. But remember that I am only a (experienced) user of SheepShaver and BasiliskII, not a developer. I filed issues I encountered as a user with builds created with recent source. I do not intend to change anything myself, I would not know how to, I hope others will solve the problems.

"Clone repository"? "Working directory"? What is my working directory? Do I have one?

I only want to be able to download the source of certain dates, to build the application from it, so I can see and report when a problem starts. That could provide information about where to look for the code that is responsible.

With CVS I knew the commands needed to do that, and I did so on several occasions. But I do not know how to do that with GitHub. Your instructions presuppose knowledge I do not have and possibly need software on my Mac I do not have installed. So far, I only accessed cebix/macemu with a web-browser and there I see only one link to download the latest revision as zip archive. I don't think I want or need the whole repository and history.

Best,  Ronald.


Op 28 jun. 2012, om 20:09 heeft Giulio Paci het volgende geschreven:

> On 28/06/2012 19:13, Ronald P. Regensburg wrote:
>> 
>> I started to file issues with SheepShaver OSX here:
>> 
>> https://github.com/cebix/macemu/issues
>> 
>> I hope someone will look into these issues. More will follow.
>> 
>> An important issue is that SheepShaver OSX appears to have lost the ability to mount CD-ROMs sometime in the past few months. I have no experience with GitHub and I do not know how to narrow the issue down to a specific patch. With CVS I used to download the source from different dates to see where a specific issue appeared. Can that be done here as well? How?
> 
> 1) When you clone a repository (e.g., git clone
> https://github.com/cebix/macemu.git) you have the whole history in the
> .git directory in your working directory.
> 
> You can get a specific revision with the checkout command (e.g.: git
> checkout <hash_tag_of_the_revision>). This will change the content of
> your working directory with those of the desired revision.
> 
> You can get the revisions history (with hash tags) with the log command.
> You can see which files have been changed with "git log --raw".
> 
> You can also compare directly two revisions with the diff command.
> 
> You can also have a look at the bisect command.
> 
> Remember that you also can do "git help command" to get help.
> 
> 2) If you want to change something and not just find the revision that
> introduced the bug, I suggest to use the fork button on github and clone
> your repository instead of the main one. This will simplify merging your
> changes in the main repository later.
> 
> Bests,
> 	Giulio.

Re: [B2-devel] Various issues SheepShaver OSX

[Alexander v. G. <kal...@un...>]

On 28.06.2012 12:13, Ronald P. Regensburg wrote:
> I started to file issues with SheepShaver OSX here:
>
> https://github.com/cebix/macemu/issues
>
> I hope someone will look into these issues. More will follow.
>
> An important issue is that SheepShaver OSX appears to have lost the 
> ability to mount CD-ROMs sometime in the past few
> months. I have no experience with GitHub and I do not know how to narrow 
> the issue down to a specific patch. With CVS
> I used to download the source from different dates to see where a specific 
> issue appeared. Can that be done here as
> well? How?


git has a great feature for finding regressions called bisect

http://webchick.net/node/99
http://alblue.bandlem.com/2011/07/git-tip-of-week-git-bisect.html

you provide a known "good" revision, and a known "bad" revision. (you don't 
*have to provide the good revision...
however it definitely narrows down the pool of all commits to tree since the 
beginning of time)

Git then will start cutting the commits in half to narrow down where the 
problem started.

  -- Alex

Re: [B2-devel] Various issues SheepShaver OSX

[Giulio P. <giu...@gm...>]

On 28/06/2012 19:13, Ronald P. Regensburg wrote:
> 
> I started to file issues with SheepShaver OSX here:
> 
> https://github.com/cebix/macemu/issues
> 
> I hope someone will look into these issues. More will follow.
> 
> An important issue is that SheepShaver OSX appears to have lost the ability to mount CD-ROMs sometime in the past few months. I have no experience with GitHub and I do not know how to narrow the issue down to a specific patch. With CVS I used to download the source from different dates to see where a specific issue appeared. Can that be done here as well? How?

1) When you clone a repository (e.g., git clone
https://github.com/cebix/macemu.git) you have the whole history in the
.git directory in your working directory.

You can get a specific revision with the checkout command (e.g.: git
checkout <hash_tag_of_the_revision>). This will change the content of
your working directory with those of the desired revision.

You can get the revisions history (with hash tags) with the log command.
You can see which files have been changed with "git log --raw".

You can also compare directly two revisions with the diff command.

You can also have a look at the bisect command.

Remember that you also can do "git help command" to get help.

2) If you want to change something and not just find the revision that
introduced the bug, I suggest to use the fork button on github and clone
your repository instead of the main one. This will simplify merging your
changes in the main repository later.

Bests,
	Giulio.

[B2-devel] Various issues SheepShaver OSX

[Ronald P. R. <ron...@xs...>]

I started to file issues with SheepShaver OSX here:

https://github.com/cebix/macemu/issues

I hope someone will look into these issues. More will follow.

An important issue is that SheepShaver OSX appears to have lost the ability to mount CD-ROMs sometime in the past few months. I have no experience with GitHub and I do not know how to narrow the issue down to a specific patch. With CVS I used to download the source from different dates to see where a specific issue appeared. Can that be done here as well? How?

Ronald.

Re: [B2-devel] Inline Assembly Query

[Charles S. <bas...@ch...>]

On Jun 28, 2012, at 7:42 AM, Alexander von Gluck wrote:

> The trick is using an older Xcode (4.0.x) *or* using this:
> https://github.com/kennethreitz/osx-gcc-installer

Ack, that installer puts stuff not only in /usr/bin, /usr/lib, etc. instead of /usr/local, but it even puts stuff in /System. That is very icky for a third-party installer, and it doesn’t seem to work any better than ‘port install apple-gcc42’ does, having the same problem with abi::__cxa_demangle() not working.

Charles