Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
so, umm are you saying it wont work? what would be the best way for me to compress a file for use on a mac? (.sit .bin .hqx .zip .rar...) what should i use?
------------------ A warrior can shape himself to suit anything in the universe. A master can shape the universe to suit himself.
For everyone to be able to use it, take the mac version and use Stuffit with MacBinary encoding.
It sucks, but it will work.
-reg
------------------ "As a rule we believe as much as we can. We would believe everything if only we could." ~ William James
Ummmm, Regulus, my understanding was that a .rsrc (atleast the kind stuffit makes) was flat, but that it was "mac binary encoded", evidenced by the fact that: A. a mac plugin file transfered mac->pc via an ftp client that macbinary encodes stuff with resource forks can be dropped onto the plug converter (ie, plug converter supports macbinary) B. the option in stuffit PC 7.5 that makes the .rsrc, .rsc, or mysterious extensionless files is "MacBinary encode extracted files when file has a resource fork" C. People have said it is. I think this is why there are problems with the transmission of .rsrc's - things along the way try to interpret the macbinary encoding and do stuff to it that ends up destroying it.
That said, Reg, the ideal way in my opinion to make a universal plugin is to macbinary encode the mac plugin, and then, not stuffit it, but to zip it. The main problem with plug usability on the PC is that stuffit has a wide variety of problems. A zipped .bin file can be unzipped and de-binned (propably all in one step, knwoing stuffit mac) with no problem on a mac. A zipped .bin file can be unzipped and the bin dropped onto the converter under windows. I plan to release my plugins as zipped .bins. -Az
------------------ It is here. EVNEW Public Beta (url="http://"http://www.aznt.com/EVN/EVNEW")www.aznt.com/EVN/EVNEW(/url) Stuffit is a piece of .sit.
Quote
Originally posted by Azratax2: Ummmm, Regulus, my understanding was that a .rsrc (atleast the kind stuffit makes) was flat, but that it was "mac binary encoded", evidenced by the fact that:
What you're talking about is a macbinary encoded file. It still has two forks, they're just multiplexed. I don't know why Stuffit is putting a .rsrc extension on anything; it shouldn't. A real .rsrc is something else, which I've explained, and is not what PC Nova uses, although it probably should. Your confusion is understandable if you aren't really familiar with Carbon apps in OS X.
That said, Reg, the ideal way in my opinion to make a universal plugin is to macbinary encode the mac plugin, and then, not stuffit it, but to zip it.
I agree. I had thought Stuffit was essential for decoding the .bin on the PC side, but on reflection you are correct.
(This message has been edited by Regulus (edited 02-12-2004).)
Originally posted by Regulus: **What you're talking about is a macbinary encoded file. It still has two forks, they're just multiplexed. I don't know why Stuffit is putting a .rsrc extension on anything; it shouldn't. A real .rsrc is something else, which I've explained, and is not what PC Nova uses, although it probably should. Your confusion is understandable if you aren't really familiar with Carbon apps in OS X.
**
Would I be interpreting this as meaning that a mac binary format is a means of putting the two forks into a file that only has a data fork?
I dont think anyone knows why stuffit (esp. winstuffit) does anything that it does, not even the people who wrote it. To call it "quirky" is being kind. -Az by the way, not only am I not familiar with carbon apps in X, I am not familiar with any mac apps in any mac os. All I know about working with a mac is that I cant make them work. I get along much better with my pc.
(This message has been edited by Azratax2 (edited 02-12-2004).)
Originally posted by Azratax2: Would I be interpreting this as meaning that a mac binary format is a means of putting the two forks into a file that only has a data fork?
Correct - it's a specific way of encoding both forks (as well as the various pieces of Mac metadata that matter) into the data fork of a single text file. It's not that common any more (it's mostly been supplanted as StuffIt has improved), but it's still occasionally useful. You may also hear of 'BinHex', which is an older version of the same thing.
------------------ David Arthur | (url="http://"http://davidarthur.evula.net/")davidarthur.evula.net(/url) | (url="http://"http://www.ev-nova.net/")EV-Nova.net(/url) The people united can never be ignited!
(This message has been edited by David Arthur (edited 02-12-2004).)
Regulus is more coherent about .rsrc files
Regulus, you're my hero.
-STH
------------------ "Create enigmas, not explanations." -Robert Smithson
okay people, in plain english please. what steps do i take from a PC, to make it macintosh compatible?
1.) Transfer the .rez file to a Macintosh.
2.) Run David Arthur's (url="http://"http://www.ambrosiasw.com/cgi-bin/vftp/show.pl?product=evn&category;=utilities&display;=date&file;=MacPluginConvertor.sit")converter(/url) on it. This will transform the .rez into a macintosh plugin.
3.) Find a macintosh tool that will encode into MacBinary format (.bin). This is not the same as BinHex (.hqx). Although Stuffit 7 supported this, Stuffit 8 does not appear to. Thus, the old (url="http://"http://www.lazerware.com/FTP/DropMacBinary_III.sit.hqx")DropMacBinary III(/url) is probably your best bet. This will require classic.
4.) Compress the .bin using your tool of choice. Azratax and I agree that .zip is probably best. In Mac OS X 10.3 you can do this via a contextual menu (control-click on the file and select Create Archive of...). In older versions, you can probably use DropZip. You could also transfer the .bin back to your PC (it won't get corrupted now) and compress it there.
That's it. Between Stuffit and Contraband, though, this really couldn't be more obtuse.
Originally posted by Cunjo: **okay people, in plain english please. what steps do i take from a PC, to make it macintosh compatible?
Get it onto a mac or emulated mac as a .rez file Run it through David Arthur's Mac Plugin Converter 1.01. Run this through a macbinary-encoder or FTP it to a PC based server with fetch (which auto-macbinary's it). From an emulated mac, copying the file with HFV explorer will also do the encoding for you. Zip the result. You now have a plug that is easy for both pc users and mac users to use. -Az
Originally posted by Azratax2: **Get it onto a mac or emulated mac as a .rez file Run it through David Arthur's Mac Plugin Converter 1.01. Run this through a macbinary-encoder or FTP it to a PC based server with fetch (which auto-macbinary's it). From an emulated mac, copying the file with HFV explorer will also do the encoding for you. Zip the result. You now have a plug that is easy for both pc users and mac users to use. -Az
thank you.
Originally posted by Azratax2: Run this through a macbinary-encoder or FTP it to a PC based server with fetch (which auto-macbinary's it).
I'm designing the whole of my TC, STN:TFF, on a WinXP machine using EVNEW, so I'll need to get my tester guys to do the Mac conversion.
Erm...in case my Mac guys ask me for one...what is a macbinary-encoder? Where can I get one? Or does it come with the MacOS system?
Thanks for the help.
P.S. EVNEW is the best! Thanks Aprosenf. I wouldn't be able to do my TC if it wasn't for you.
------------------ STN: The Final Frontier - ( (url="http://"http://digitalspain.net")Oficial web site...(/url) | (url="http://"http://www.ambrosiasw.com/webboard/Forum26/HTML/015591.html")Discussion in Ambrosia...(/url) | (url="http://"http://ev-nova.net/forums/viewtopic.php?t=5005&sid;=d0a4307ce254d6054c3e2d7221ff1984")Discussion in EV-Nova.net...(/url) )
th macbinary encoder is a feature of Stuffit, stuffit lets you encode files in different ways before stuffing/ziping them, it also lets pc users hang on to the rescource forks of files, by copying them over to the data fork.
Originally posted by Cunjo: **th macbinary encoder is a feature of Stuffit, stuffit lets you encode files in different ways before stuffing/ziping them, it also lets pc users hang on to the rescource forks of files, by copying them over to the data fork.
Thanks.
So it's quite simple really! And there I was, all worried!
Not Stuffit 8, though, because Aladdin is a pain in the ass. Follow my link above to "DropMacBinary III", which will run under classic.
Also, if you run an FTP server on the PC as your way of getting files to it from the mac, Fetch will automaticly macbinary them for you, so the process would be: 1. download from PC server to mac with fetch 2. Convert 3. upload to pc server 4. zip on PC. For readme, include two copies, and use a program like textpad on pc to save a mac and PC version of the readme text file (otherwise mac's wont interpret the linebreaks right. The three main OS's all use different ways of getting a new line (one uses a carriage return, one uses a linefeed, and one uses both. I have long since forgotten which is which). Yes, I said "carriage return". The charachter set used on all computers is based on the one they used in teletypes. -Az
(This message has been edited by Azratax2 (edited 02-15-2004).)
Originally posted by Azratax2: The three main OS's all use different ways of getting a new line (one uses a carriage return, one uses a linefeed, and one uses both. I have long since forgotten which is which).
Macs use a carriage return (character 13), while UNIX uses a linefeed (character 10). DOS (and therefore Windows) uses a carriage return followed by a linefeed.
David - since the MacBinary spec is published, would it be possible for you to modify your converter to translate .rez files into resource-fork plugins in .bin format? It seems like it would save some people a step or two.
Originally posted by Regulus: David - since the MacBinary spec is published, would it be possible for you to modify your converter to translate .rez files into resource-fork plugins in .bin format? It seems like it would save some people a step or two.
I'll look into it. It might be possible, although it would make the program a bit more complex (at the moment, it never accesses the resource fork directly, but rather uses the Resource Manager to create the resources it finds in the .rez file).
Originally posted by David Arthur: **I'll look into it. It might be possible, although it would make the program a bit more complex (at the moment, it never accesses the resource fork directly, but rather uses the Resource Manager to create the resources it finds in the .rez file).
Hmmm. Could you do something like bundle it with a macbinary encoder, then create the file like you do now, and then have it just call the encoder? It would be kinda hackjoby, but it would propably be alot easier to add the feature in... -Az