It is NOT your ISP's responsibility to notify you of who does NOT have access. It is you ISP's job to ensure that your pages are available to anyone wants access (and can fulfill a set of requirements to include 'can view web pages').
Your ISP absolutly fulfilled their contract and being censored (in appropriatly) is totally beyond their control -- weather they had knowledge or not they should have no need to inform you.
Your ISP (if it's anything like mine) does a hell of a lot more than 'serve your web pages'. Do you have a business accout? There is a reason you'd pay more for that. There is typically no gaurantee of service for non-business class services. You might want to think about that if you plan on getting DSL through some place like US West. No DSL connection? Not our problem we'll get to when we get to it. Want everything ASAP? pay for it.
For these reasons I feel a Linux standard is needed; otherwise developing for "Linux" will be too much of a pain for companies and it won't really happen. If not that, then software development companies will all eventually gravitate toward one proprietary version of Linux, and we'll have the Micro$oft effect all over again; the oppressed will become the oppressor.
Not really, some distros may have to become 'compliant' (at worst). Say you have debian and you need to run some 'RH Only' package, debian would, I suspect, have a RH-Emul package you could install.
The only way I see this really happening is if some distro contained something truly closed and proprietary. I just do see this happening any time soon. Besides which, what kind of brain-dead company would choose to only develop for some proprietary feature in an otherwise free/open OS? I suspect we don't need that kind of hypothetical software anyway (How wonderful could it be, given the already short sightedness of creators?).
p241 K&R Ansi C: External identifiers that begin with an undersocre are reserved for use by the library [variables, functions, etc]. as are all other identifiers that begin with an underscore and an upper-case letter or another underscore [#define'd macros].
More clearly:
extern char * _some_buffer;
and #define _A_something #define __other_macro
are all 'reserved'
whereas extern char * myvar; and #define _x_Macro
would all be fair game for you to use in your program.
So if I used 'header gaurds' of #ifndef _header_graphic_h_ That's really just fine, but if I #ifndef __header or #ifndef _Header
I may risk clashing with the C library, and I was warned.
The idea that the complier could refuse the complie the code is silly of course... It has to compile the C library doesn't it?
DA: Now Microsoft is primarily a software company, but you actually got into some important hardware development with the Mouse. Do you want to say a few words about that?
BG: Microsoft was playing a much broader role[laughs] than just doing software for this machine. I mean whether it is the keyboard, the character set, the graphics adapter, or even the memory layouts. I laid out memory so the bottom 640K was general purpose RAM and the upper 384 I reserved for video and ROM, and things like that. That is why they talk about the 640K limit. It is actually a limit, not of the software, in any way, shape, or form, it is the limit of the microprocessor. That thing generates addresses, 20-bits addresses, that only can address a megabyte of memory. And, therefore, all the applications are tied to that limit.
It was ten times what we had before. But to my surprise, we ran out of that address base for applications within -- oh five or six years people were complaining.
Another thing that Microsoft did, in terms of getting these new machines out there and really showing off what new uses they could be put to, was we came out with our own mouse product. The mouse was invented by Doug Englebart back at Stanford Research Institute. Xerox used it in the Alto, the research machine that PARC built, has a three-button device. The Star had a two-button mouse. And then went Apple went and did a mouse, they did a single-button. We believed the two-button concept was the right approach. So, we went to a Japanese company, Alps, got them to do some design work, paid the patent fees to SRI and Xerox for this, and came out with this as a low-cost add-on. So, even on a character-mode display, being able to move the cursor around in a natural way, we thought was a big advantage. We tied it to Word so that we had a bundle with Word and the Mouse. But then people who didn't like the Mouse thought they shouldn't buy Word. So, it was a little bit of a problem.
When we first brought this out we ordered 50,000 and it took over a year to sell the first 50,000. Today we sell many, many hundreds of thousands in a month. But, at first it looked like maybe we had made a mistake. This did go on to be a very profitable thing for us and we continued to evolve the design going to a sleeker and sleeker appearance over time.
Funny, I was just starting a GTK to OS/2 PM port and noticed this in the win32 mods to glib: [From memmory] PeekMessage( MGG *, HWND, NULL, 0, 0, PM_NOREMOVE);
Compaq's license isn't the same as other manufactures either [Compaq makes modifications to Win9x from what I've seen]. My brother got a Compaq Laptop and it had a custom version of 95. He tried to install MS Office on it [95 I think] and it failed. He asked me to help, same problem. We called compaq support and the rep said that you couldn't do the default install of MS Office on (and have it work). You were supposed to by Compaq's version of MS Office for it. Obviously I recommed that ppl DON'T BUY COMPAQ.
Most of the Basic code for the altair was hacked up basic Bill borrowed from DEC (where he worked for a time). The math (Floating) was done by a third person.
Dos = QDos = Not anything related to Bill.
Bill pushed his begged borrowed and stolen basic interp. as far as he could. He would usually promise schedules he knew he couldn't make (clean) just to get the $$. (Knowing he'd upsell a fixed basic rom to the end user).
Steve Jobs is NOT a hacker. Woz IS. All steve did was coax Woz into building the Apple (Woz had built a keyboard that amazed Jobs).
BTW: The key to Gates success is in the business acumen of Paul, notice how MS OEM Lic. looks really similar to TicketMaster? Duh...
According to the http://www.usdoj.gov/atr/cases/f0000/0047.htm If model ip3xyz ships with 'free' windows 98 the OEM is charged for that license. OEM needs to ship model a computer with a different model number to escape the charge.
The best scenario for Free/OSS is that this is true, and that she isn't interested in the profits of this patent. Then she could patent this algorithm, using The League for Programming Freedom This would add a patent to the pool we will need, not that software can be patented.
Would be nice if someone let her know her options.
Wouldn't it be really cool if some of this was dedicated to grants to Open Source projects?
It is NOT your ISP's responsibility to notify you of who does NOT have access. It is you ISP's job to ensure that your pages are available to anyone wants access (and can fulfill a set of requirements to include 'can view web pages').
Your ISP absolutly fulfilled their contract and being censored (in appropriatly) is totally beyond their control -- weather they had knowledge or not they should have no need to inform you.
Your ISP (if it's anything like mine) does a hell of a lot more than 'serve your web pages'. Do you have a business accout? There is a reason you'd pay more for that. There is typically no gaurantee of service for non-business class services. You might want to think about that if you plan on getting DSL through some place like US West. No DSL connection? Not our problem we'll get to when we get to it. Want everything ASAP? pay for it.
First? I think not. http://www.qnx.com/hotnews/pr/teligent.html
For these reasons I feel a Linux standard is needed; otherwise developing for "Linux" will be too much of a pain for companies and it won't really happen. If not that, then software development companies will all eventually gravitate toward one proprietary version of Linux, and we'll have the Micro$oft effect all over again; the oppressed will become the oppressor.
Not really, some distros may have to become 'compliant' (at worst). Say you have debian and you need to run some 'RH Only' package, debian would, I suspect, have a RH-Emul package you could install.
The only way I see this really happening is if some distro contained something truly closed and proprietary. I just do see this happening any time soon. Besides which, what kind of brain-dead company would choose to only develop for some proprietary feature in an otherwise free/open OS? I suspect we don't need that kind of hypothetical software anyway (How wonderful could it be, given the already short sightedness of creators?).
p241 K&R Ansi C:
... It has to compile the C library doesn't it?
External identifiers that begin with an undersocre are reserved for use by the library [variables, functions, etc]. as are all other identifiers that begin with an underscore and an upper-case letter or another underscore [#define'd macros].
More clearly:
extern char * _some_buffer;
and
#define _A_something
#define __other_macro
are all 'reserved'
whereas
extern char * myvar;
and
#define _x_Macro
would all be fair game for you to use in your program.
So if I used 'header gaurds' of
#ifndef _header_graphic_h_
That's really just fine, but if I
#ifndef __header
or
#ifndef _Header
I may risk clashing with the C library, and I was warned.
The idea that the complier could refuse the complie the code is silly of course
--Shaun
Is this better? http://www.si.edu/resource/tours/comphist/gates.ht m#tc44
Microsoft and the Mouse
DA: Now Microsoft is primarily a software company, but you actually got into some important hardware development with the Mouse. Do you want to say a few words about that?
BG: Microsoft was playing a much broader role[laughs] than just doing software for this machine. I mean whether it is the keyboard, the character set, the graphics adapter, or even the memory layouts. I laid out memory so the bottom 640K was general purpose RAM and the upper 384 I reserved for video and ROM, and things like that. That is why they talk about the 640K limit. It is actually a limit, not of the software, in any way, shape, or form, it is the limit of the microprocessor. That thing generates addresses, 20-bits addresses, that only can address a megabyte of memory. And, therefore, all the applications are tied to that limit.
It was ten times what we had before. But to my surprise, we ran out of that address base for applications within -- oh five or six years people were complaining.
Another thing that Microsoft did, in terms of getting these new machines out there and really showing off what new uses they could be put to, was we came out with our own mouse product. The mouse was invented by Doug Englebart back at Stanford Research Institute. Xerox used it in the Alto, the research machine that PARC built, has a three-button device. The Star had a two-button mouse. And then went Apple went and did a mouse, they did a single-button. We believed the two-button concept was the right approach. So, we went to a Japanese company, Alps, got them to do some design work, paid the patent fees to SRI and Xerox for this, and came out with this as a low-cost add-on. So, even on a character-mode display, being able to move the cursor around in a natural way, we thought was a big advantage. We tied it to Word so that we had a bundle with Word and the Mouse. But then people who didn't like the Mouse thought they shouldn't buy Word. So, it was a little bit of a problem.
When we first brought this out we ordered 50,000 and it took over a year to sell the first 50,000. Today we sell many, many hundreds of thousands in a month. But, at first it looked like maybe we had made a mistake. This did go on to be a very profitable thing for us and we continued to evolve the design going to a sleeker and sleeker appearance over time.
http://www.vcnet.com/bms/departme nts/catalog.html
This doens't include the Windows-OS/2 forked/concurrent development IIRC.
WTF: This 486 w/16M needs an upgrade, maybe you can /. it
http://shaun.tancheff.com/NtMag.html
Funny, I was just starting a GTK to OS/2 PM port and noticed this in the win32 mods to glib:
[From memmory]
PeekMessage( MGG *, HWND, NULL, 0, 0, PM_NOREMOVE);
The OS/2 PM Eqiv of:
WinPeekMsg( HAB, QMSG *, HWND, NULL, 0, 0, PM_NOREMOVE );
I guess that somebody decided that the PM_NOREMOVE must be PeekMessage not Presentation Manager so they didn't have to change the constant.
Sorry, but I found it hilarious.
If anybody else is working on a PM port of GTK I'd be interrested in working with them.
shaun@tancheff.com
Ya never know what gripe you're gonna have next.
Maybe a china-slave-labor-products.blacklist.org might be nice too.
I'm against a lot of stuff.
Compaq pays as much as $75 per PC? Ouch.
Compaq's license isn't the same as other manufactures either [Compaq makes modifications to Win9x from what I've seen]. My brother got a Compaq Laptop and it had a custom version of 95. He tried to install MS Office on it [95 I think] and it failed. He asked me to help, same problem. We called compaq support and the rep said that you couldn't do the default install of MS Office on (and have it work). You were supposed to by Compaq's version of MS Office for it. Obviously I recommed that ppl DON'T BUY COMPAQ.
Most of the Basic code for the altair was hacked up basic Bill borrowed from DEC (where he worked for a time). The math (Floating) was done by a third person.
Dos = QDos = Not anything related to Bill.
Bill pushed his begged borrowed and stolen basic interp. as far as he could. He would usually promise schedules he knew he couldn't make (clean) just to get the $$. (Knowing he'd upsell a fixed basic rom to the end user).
Steve Jobs is NOT a hacker. Woz IS. All steve did was coax Woz into building the Apple (Woz had built a keyboard that amazed Jobs).
BTW: The key to Gates success is in the business acumen of Paul, notice how MS OEM Lic. looks really similar to TicketMaster? Duh...
Maybe.
According to the http://www.usdoj.gov/atr/cases/f0000/0047.htm If model ip3xyz ships with 'free' windows 98 the OEM is charged for that license. OEM needs to ship model a computer with a different model number to escape the charge.
The best scenario for Free/OSS is that this is true, and that she isn't interested in the profits of this patent. Then she could patent this algorithm, using The League for Programming Freedom This would add a patent to the pool we will need, not that software can be patented.
Would be nice if someone let her know her options.