From: runehh@dhhalden.no (RUNE HALFDAN HOLST HUSEBY)
Subject: Re: Macintosh bigots
Organization: Ostfold College
Date: Mon, 16 Nov 1992 16:56:05 GMT

In article <00t1hlb@rpi.edu> johnsd2@jec314.its.rpi.edu.its1 (Daniel Norman Johnson) writes:
>>That's quite similar to a Windows metafile. Two excerpts from the
>>online Windows 3.0 SDK helpfile:
>>
>[deletia- Metafile description]
>
>Nifty! I guess you guys do have something PICT. Do this have
>to be files? Can you put one in the clipboard, or make one
>a resource?
Metafiles can be files, it can be put on the clipboard. I'm not quite sure
if it is any special resource tpe 'Metafile', like cursors and icons, but 
you can have user-define resources, where you can have absolutely anything, 
including metafiles

>>You don't, if you only need simple sounds. There is always the 
>>speaker.
>
>Which can only beep under Windows, no? Or did windows pick up a driver
>for the internal speaker that I dont know about?
There is a driver for the internal speaker you don't know about. It's OK as 
long as you don't need noise-free sound.

>>Do all Macintoshs have 32 bit access to the video memory?
>
>Yes; All that I know of anyway. Im not entirely sure about the Classic,
>Plus or whatnot but having b&w display only would compensate.
How can this be, when not all Mac's don't even have 32-bits memory 
addressing? On our Mac IIcx, on which we *need* a whole lot of memory, we 
must emulate 32-bits addressing, which causes the system (7) to be 
*extremely* unstable. (avg. 1 crash/hour).

>>They're starting to sell S3 cards for 450 DM (about 290$) here in 
>>Germany. When bundled with a machine, you'll probably get it for
>>less.
>
>How deep is this cards display? How many pixels does it produce?
Not quite sure about this. I think some is capable of 24-bit in some modes.
This usually depends on how much video-mem you have.

>>>>>As for the kludgy thing, sure looks kludgy to me. You still have to
>>>>>have separate files for your (non-editable) resources, right? Kludge!
>>>>
>>>>Resources are editable with programmers' tools. Users don't have to edit
>>>>resources. And they're easier to use for multiple executables if they are
>>>>in separate files (any executable can share a DLL).
>>
>>>But you MUST put them in separate files- ALWAYS. This means that
>>>a program CANNOT be one file. That sux.
>>
>>This is not true, plain and simple.
>>
>>Because I don't understand what you refer to, would you care
>>to explain your statement?
>
>Hey, now waitasec. If you dont understand what I am saying,
>how come you are assertting that it is not true?
>
>I am saying that:
>	- Windows programs must have SEPARATE resource files-
>	  you cant put the resources in the .EXE.
>	- You will virtually always need (or at least want) to use
>	  resources in windows programs.
>	- Doing so requires some sort of resource file.
>	- Hence, Windows program require a separate resource file,
>	- Hence Windows programs can't live in one file only.
>
>Which part is wrong?
Part 1,3,4 and 5

Resources is either part of the .EXE, *OR* part of a seperate .DLL.
A .DLL (dynamic link library) is a file with resources and/or executable 
code, which, as the name implies, is loaded into memory, during run-time 
whenever you need it.


>---
>			- Dan Johnson
>And God said "Jeeze, this is dull"... and it *WAS* dull. Genesis 0:0
>
>These opinions have had all identifiying marks removed, and are untraceable.
>You'll never know whose they are.

															 }  } {  {
/-------------------------------}--}--{+-----------------------------------\
|   Rune Halfdan Holst Huseby    }  {  |      Ostfold Regional College     |
|  ____________________________   }{   |               Halden              |
| (_____(_runehh@dhhalden.no___##}     |               NORWAY              |
|--------------------------------------+-----------------------------------|
| Real programmers never work 9 to 5. If any real programmers are around   |
| at 9 am, it's because they were up all night.                            |
\--------------------------------------------------------------------------/