I couldn't find anything in the terms of service for Verizon when I had them a year or so ago. I asked lots of people at Verizon, and eventually got pushed up past the regular tech support to people who said their "internal" TOS documents said servers were fine, but you just had to deal with the ports 25 and 80 being blocked, and the upstream slow speed.
I didn't bother telling them that port 25 is not blocked. Port 80 was, and running the web server on 8000 eventually annoyed me enough to switch to speakeasy.
Hrm. Maybe that doesn't apply to me because I am considered a "business customer" in their eyes.
As far as I can tell, the only reason I am considered a business customer, is I talked to a sales person and asked him a bunch of questions before ordering, and to get me to sign up for a more expensive plan, he gave me a $10/month discount.
And, from then on, they put me in a special queue, for business customers, and a "Dedicated Account Manager", though I don't know if that is really anything special or not.
I do have more services, ie. email address/DNS hosting than other speakeasy customers I know of...
Try Speakeasy. As one of their tech support told me the other day, "That's the great thing about Speakeasy, you buy the connection from us, and then do whatever you want with it."
That was in response to, "can I sell wireless internet to my neighbors, and not tell you about it?"
Dynavox Systems have devices to allow access to computers, etc. That might be an option. Health insurance might cover the cost of purchasing the device, particularly if he has trouble communicating.
PS. I work for them, but please don't hold that against them.
Re:Email Should be granted post priority
on
Verizon vs. Europe
·
· Score: 1
I would have called, but your VOIP phone is blocking my packets, since it thinks they are spam.
Not true. At least for most of the WinCE code base.
For example, there is a bug in the IrDA driver. I spoke with Microsoft, they agreed it was a bug, asked for my code fix, have not yet patched the kernel (last time I looked)
But, our version of the kernel works fine.
PS. The bug is ironically commented that it is a bug in HP printers. Presumably HP was broken at some point, and so Microsoft hacked their code to work with the HP printers, but their fix was incorrect. HP has now fixed it in their printers (or at least the ones I am using), but the Microsoft code no longer matches the IrDA specification, and so some HP printers print really slowly, if at all.
I don't know about XP embedded but for CE, we can modify a good portion of the kernel code. I don't know the exact percentages, but I would guess 80%.
Yes, there have been times that we wish we could modify other parts, but it hasn't been too bad.
WinCE 4.2 does seem to be more restrictive than previous versions -- haven't looked into it too much yet.
I don't know what the license agreements are in terms of modifying the so-called "private" code, as opposed to just the "public" code. If modifying the private code isn't allowed, then the parent has a pretty good point, as that probably shrinks the percentage of modifiable code to 50% or less.
It seems strange to me -- different people reporting different results. I don't get any popups at all. Apparently, secunia's thing is somehow breaking the javascript or something, as I am using firefox 1.0 on windows 2000, fully patched, and nothing happens.
> Pick one or the other -- either you're talking
> about win9x and the weak security argument holds
> up, or you're talking about NT and the "billions
> of dollars" argument could make a fair case, but
> not both.
Ok, I will pick NT and 2000. Take a look at the password security. Passwords are encoded in seven letter chunks. By default, these passwords are sent across the network, where it is extremely easy to decode them. Even if you set it to the highest security, the seven letter restriction still applies, and the passwords are still stored in the LM format, so if you want to crack them, you don't have to bother with the "high security" hashes, since the practically plaintext versions are sitting right there.
And, if you want to connect to any win95/98/etc computer, you need to leave security on low, and any NT/2000 machine cannot connect either, until it is upgraded as well.
Horrible security, whether you are talking about 95 or NT.
I couldn't find anything in the terms of service for Verizon when I had them a year or so ago. I asked lots of people at Verizon, and eventually got pushed up past the regular tech support to people who said their "internal" TOS documents said servers were fine, but you just had to deal with the ports 25 and 80 being blocked, and the upstream slow speed.
I didn't bother telling them that port 25 is not blocked.
Port 80 was, and running the web server on 8000 eventually annoyed me enough to switch to speakeasy.
Hrm. Maybe that doesn't apply to me because I am considered a "business customer" in their eyes.
As far as I can tell, the only reason I am considered a business customer, is I talked to a sales person and asked him a bunch of questions before ordering, and to get me to sign up for a more expensive plan, he gave me a $10/month discount.
And, from then on, they put me in a special queue, for business customers, and a "Dedicated Account Manager", though I don't know if that is really anything special or not.
I do have more services, ie. email address/DNS hosting than other speakeasy customers I know of...
Try Speakeasy.
As one of their tech support told me the other day, "That's the great thing about Speakeasy, you buy the connection from us, and then do whatever you want with it."
That was in response to, "can I sell wireless internet to my neighbors, and not tell you about it?"
Dynavox Systems have devices to allow access to computers, etc.
That might be an option.
Health insurance might cover the cost of purchasing the device, particularly if he has trouble communicating.
PS. I work for them, but please don't hold that against them.
I would have called, but your VOIP phone is blocking my packets, since it thinks they are spam.
(:
Not true. At least for most of the WinCE code base.
For example, there is a bug in the IrDA driver. I spoke with Microsoft, they agreed it was a bug, asked for my code fix, have not yet patched the kernel (last time I looked)
But, our version of the kernel works fine.
PS. The bug is ironically commented that it is a bug in HP printers. Presumably HP was broken at some point, and so Microsoft hacked their code to work with the HP printers, but their fix was incorrect. HP has now fixed it in their printers (or at least the ones I am using), but the Microsoft code no longer matches the IrDA specification, and so some HP printers print really slowly, if at all.
I don't know about XP embedded but for CE, we can modify a good portion of the kernel code. I don't know the exact percentages, but I would guess 80%.
Yes, there have been times that we wish we could modify other parts, but it hasn't been too bad.
WinCE 4.2 does seem to be more restrictive than previous versions -- haven't looked into it too much yet.
I don't know what the license agreements are in terms of modifying the so-called "private" code, as opposed to just the "public" code. If modifying the private code isn't allowed, then the parent has a pretty good point, as that probably shrinks the percentage of modifiable code to 50% or less.
It seems strange to me -- different people reporting different results. I don't get any popups at all. Apparently, secunia's thing is somehow breaking the javascript or something, as I am using firefox 1.0 on windows 2000, fully patched, and nothing happens.
> Pick one or the other -- either you're talking
> about win9x and the weak security argument holds
> up, or you're talking about NT and the "billions
> of dollars" argument could make a fair case, but
> not both.
Ok, I will pick NT and 2000. Take a look at the password security. Passwords are encoded in seven letter chunks. By default, these passwords are sent across the network, where it is extremely easy to decode them. Even if you set it to the highest security, the seven letter restriction still applies, and the passwords are still stored in the LM format, so if you want to crack them, you don't have to bother with the "high security" hashes, since the practically plaintext versions are sitting right there.
And, if you want to connect to any win95/98/etc computer, you need to leave security on low, and any NT/2000 machine cannot connect either, until it is upgraded as well.
Horrible security, whether you are talking about 95 or NT.