[Beowulf] Wired article about Go machine
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Joshua Baker-LePain jlb17 at duke.eduThu Mar 26 10:23:05 PDT 2009
- Previous message: [Beowulf] Wired article about Go machine
- Next message: [Beowulf] mvapich2 does not run successfully mpi1 application
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, 26 Mar 2009 at 10:17am, Lux, James P wrote >> From: beowulf-bounces at beowulf.org >> [mailto:beowulf-bounces at beowulf.org] On Behalf Of Joshua Baker-LePain >> >> Note that Leif mentioned medical equipment with embedded >> Windows systems. >> And he's right -- you're not allowed to touch the software >> build on those without getting the new build approved by the >> FDA (at least, not if you want to use said equipment on real >> live patients). And those machines are generally networked >> so that the data (images, e.g.) can be uploaded. It is very, >> very scary. Why anyone ever made the decision to run medical >> equipment on Windows (over the screams of the engineering >> team) is utterly beyond me. > > Not to be a MS fanboy, but it should also be recognized that Windows > Embedded is a different animal than consumer Windows. Or, more properly, > Windows Embedded CAN be made a different animal. It's up to the system I should have clarified that when I said "embedded" above I didn't mean "Embedded". The equipment I was obliquely referring to was running bog standard XP. *shudder* -- Joshua Baker-LePain QB3 Shared Cluster Sysadmin UCSF
- Previous message: [Beowulf] Wired article about Go machine
- Next message: [Beowulf] mvapich2 does not run successfully mpi1 application
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
