This isn't just a comment on these boards reviewed here, but on small form factors and integrated graphics in general: why can't they make them with DVI video outputs? I mean, you're not going to be playing twitch games on these things so why not?
(hmmm.. can you say MMORPG? okay, probably not, but you can spell it, right?)
Oh well, I'd play Grim Fandango again in a second, if I hadn't finished it already. Dammit, when's the sequel coming? I never liked the monkey island series. Is it me or did GF just have a whole bunch more class?
Not such a joke. It turns out that NT (in its 2000 release) and MTS (now known as COM+) did fulfill Gate's prophecy of being good at transactions. It holds the top 2 spots and half of the Top Ten TPC-C by Performance results. Not only that, the 5 windows-based systems in the top 10 are cheaper (per tpmC) than the others.
Also, windows (2003, running on a 32-processor machine) holds 2nd position in the non-clustered results. And while the performance is within 95% of the leader, it's price is less than half.
Well, it was quite a bit more than that. It was certainly a way to run multiple DOS programs, yes. But it was also a way to run windows applications. The windows applications were 16-bit, yes, but they weren't DOS apps. Windows had its own loader, memory management, device drivers, etc...
why did it have such a problem running DOS apps?
I don't know, it seemed to work okay for me. of course, you had to be careful what kind of apps you multitasked since badly behaved apps (games, mostly) could write directly to hardware which was not virtualized as it is in NT WOW.
you couldn't double click the upper left hand corner of the window
I'm pretty sure they disabled this feature since there's no programmatic way that windows could indicate to a DOS program running in a VM that the user wishes that program to exit (or for that DOS program to tell windows 'wait a sec, I need to let the user save his/her data'). DOS historically didn't have (or need) such an API. Since windows couldn't know that closing a DOS box wouldn't result in the loss of the user's data, they disabled this feature, probably after noticing users making this mistake in usability testing. The only way to close a DOS box was to close whatever DOS program you were running, and type 'exit' at the prompt.
And then there were the memory leaks.
Yeah, unfortunately, since all applications shared the same global heap, any memory or resources leaked by an application could not be recovered. Of course, some application developers took the time to make sure their applications didn't leak.
LOL! have you ever looked at MSDOS.SYS and IO.SYS on a win95 machine? they're text files containing comments along the lines of "do not delete this file, it exists for compatibility with legacy applications". Sure you can thunk down to DOS if you want to, for compatibility, but most applications use the win32 API and the underlying 32-bit drivers - assuming your hardware vendor provided them.
yeah win95 did not have a multithreaded 'kernel', it's ring-0 code was not reentrant. but this does not mean that 32-bit applications and the set of win16 apps could not be preempted if they were in user code. it wasn't until the preempt kernel patch that linux operated in precisely that same manner - threads in the kernel would spin before continuing. when you run 16-bit apps win95 doesn't 'resort' to a less sophisticated form of multitasking the 32-bit apps, they're multitasked in exactly the same way they always are, it's just the 16-bit apps that are preempted as a single app. To do otherwise would be impossible: 16-bit apps expect to cooperatively multitask with each other; they share a single address space, message queue, global heap, the whole lot. If you wanted them to preempt each other you'd have to rewrite all the existing 16-bit apps. Not much of a compatibility feature.
actually win31 did preemptively multitask x86 real-mode VMs when you had one or more command prompts open. also it used the 386's enhanced mode to provide virtual memory (although that may have been 3.11, I can't remember).
i was thinking the same thing. the definition put forward contains:
a planet must orbit a star, not another planet, and it must be round
as far as I can see that definition is ambiguous as hell. for example which 'star' is he talking about? surely everything is in orbit around everything else? that might be a little farfetched, but it could quite easily be argued that neptune and uranus are in orbit around each other since their orbits around the sun cross periodically. how about the earth and the moon? if the sizes of the earth and moon qualify them as being planets then they are by definition NOT planets since they are in orbit around each other and a planet cannot be in orbit around another planet...
terminal services supports all resolutions and bit depths that are supported on the client. the coolest thing is that it also supports sound, you can run winamp on the server and it'll pipe the sound back to the client. it will also map your local drives and printers so they appear as local devices on the server.
How about being able to post audio clips to your blog, from your phone? This is pretty cool stuff, it currently only works with blogger, but it looks like they're trying to integrate it into other bloging software.
Slashdot Mirror
oops, sorry, left out the comma.
buy a bunch of them, give them each an axe and hook them up to Weta's Massive.
Well, you could buy a k7s5a and put a 1.3GHz Duron in it for around $80 total, and you'd still wipe the floor with the Mini-ITX.
Hello...?! McFly...?
This isn't just a comment on these boards reviewed here, but on small form factors and integrated graphics in general: why can't they make them with DVI video outputs? I mean, you're not going to be playing twitch games on these things so why not?
run 'msconfig', go to the 'Services' tab, check 'Hide all Microsoft Services', disable all of the remaining services, reboot.
Oh well, I'd play Grim Fandango again in a second, if I hadn't finished it already. Dammit, when's the sequel coming? I never liked the monkey island series. Is it me or did GF just have a whole bunch more class?
and the stringently governed, independant, industry accepted benchmarks to back up this statement are where exactly?
Also, windows (2003, running on a 32-processor machine) holds 2nd position in the non-clustered results. And while the performance is within 95% of the leader, it's price is less than half.
no, 'ring-0' implies syscalls, so I'm talking about the same thing: blocking in the kernel.
LOL! have you ever looked at MSDOS.SYS and IO.SYS on a win95 machine? they're text files containing comments along the lines of "do not delete this file, it exists for compatibility with legacy applications". Sure you can thunk down to DOS if you want to, for compatibility, but most applications use the win32 API and the underlying 32-bit drivers - assuming your hardware vendor provided them.
Your statements are not based on fact.
actually win31 did preemptively multitask x86 real-mode VMs when you had one or more command prompts open. also it used the 386's enhanced mode to provide virtual memory (although that may have been 3.11, I can't remember).
Note: some assembly required, batteries not included.
you only need the hey (removable/biometrics) when you boot, the decryption key can then be held in volatile, non-paged RAM until shutdown.
about time too. outlook over a VPN over a modem sucks ass even when you have most everything caches in a .ost file.
wtf?
terminal services supports all resolutions and bit depths that are supported on the client. the coolest thing is that it also supports sound, you can run winamp on the server and it'll pipe the sound back to the client. it will also map your local drives and printers so they appear as local devices on the server.
For that is the Tao of the Slashdot. The slash is to the yin as the dot is to the yang. They are the same yet they are different.
actually the kernel is the kernel. what you're talking about is the executive.
Microsoft's internal bug tracking system was (still is?) called RAID, for much the same reason.
How about being able to post audio clips to your blog, from your phone? This is pretty cool stuff, it currently only works with blogger, but it looks like they're trying to integrate it into other bloging software.