Talk:VxWorks

Marketing?

This appears to be almost marketing spiel, a feature and clients list, than a discussion of what it actually is. —The preceding unsigned comment was added by Achromatic (talk • contribs) .

Concur. -Mardus 16:07, 12 July 2006 (UTC)

This is Wikipedia, so you know what to do: be bold and improve the article!

Atlant 16:08, 12 July 2006 (UTC)

Cost?

Does anyone know how much this costs per seat? —The preceding unsigned comment was added by 66.238.211.199 (talk • contribs) .

It's bloody expensive, and a total bitch to use (pardon the language, but I'm trying to get the bastard to work at this very moment and it's frustrating). /Alkanen

Would I be correct in guessing that you were not a Unix programmer before you tried to use VxWorks? 'Cause if you speak Unix and understand realtime concepts, the transition to VxWorks is usually thought to be very easy. I certainly found it to be so.

Atlant 12:19, 3 October 2006 (UTC)

I am a Unix programmer. It's not the programming in VxWorks that's hard, it's getting the thing to work with hardware that's not in the default installation package (viz. Leon2) that's horrid. It might not be VxWorks that's the problem, but rather the BSP though.

I'm sure software development will be quite simple once we get advanced features like processes to even compile...

Oh, by the way. Do you happen to know a good source of documentation? The one that comes with Workbench doesn't seem to go into specifics, only general issues. We're trying to find information on how to create our own device drivers and loading them into the kernel, and most of the information we find is in the nature of "Remember not to write too large device drivers, since the kernel needs to be fast". I mean duh, we know that, but we don't know the specific function calls to make in order to create the drivers in the first place. /Alkanen

https://portal.windriver.com/windsurf/techpubs/os/vxworks/v6.4/vxworks_device_driver_developers_guide_6.4.pdf

(Wind River UID and password necessary) Fumblebruschi 17:14, 27 June 2007 (UTC)

Image

I took the liberty of moving the Orbiter image to the Products using VxWorks -section; it felt a little like an advertisement when right in the beginning of the article. If anyone disagrees, do feel free to revert. 82.181.61.48 00:18, 17 August 2006 (UTC)

(Speaking just for me), I have no problem with that. A better image to lead the article might be a fair-use screen shot of the VxWorks console (OS boot-up) splash screen; I'm pretty sure Wind River wouldn't/couldn't object to such use.

Atlant 12:55, 17 August 2006 (UTC)

Which embedded OS has the most users

I'm thinking it's vxWorks, but can't find a source 69.228.240.57 22:46, 3 August 2007 (UTC)

Competitive operating systems

This subtitle doesn't sound right to me. Competing, perhaps? —Preceding unsigned comment added by 213.139.195.162 (talk) 14:53, 22 October 2007 (UTC)

Use in HP MSA2000 RAID controllers

I added a couple of days ago that the MSA2000 line of RAID controllers from HP (developed by Dot Hill), why was that deleted? —Preceding unsigned comment added by 15.203.233.77 (talk) 13:40, 9 July 2008 (UTC)

Use in Linksys and Cisco routers

Someone should add the wrt54g series of routers to the list. 199.230.203.254 (talk) 21:35, 26 August 2008 (UTC)

Incorrect History

Actually, Wind River didn't develop VxWorks; they (originally) partnered with a company in San Jose--whose name I simply can't remember right now--who was then developing real-time OSes. Said company was purchased/acquired by NBI, which then sold off the VxWorks components to Wind River.

I would make the modification, but I don't want to rely on my memory. I know the software wasn't developed by Wind River, however; I wrote the stinkin' documentation for it. —Preceding unsigned comment added by 66.129.224.36 (talk) 22:26, 26 March 2009 (UTC) My apologies for not signing the above.Dougom (talk) 01:36, 27 March 2009 (UTC)

Memory kicked in: VxWorks was developed by a company called Integrated Solutions, Inc. (ISI) in the late 80s and early 90s. ISI was purchased/acquired by NBI of Texas.Dougom (talk) 02:41, 5 April 2009 (UTC)

Sorry to break it to you but your memory is faulty. PSOS was ISI's product. They acquired Software Component Groups and were eventually purchased by WRS. The rest is history. Buy your top competitor and shut them down. --JoelSherrill (talk) 21:22, 3 September 2009 (UTC)

I'm not trying to argue, honest, but if that's the case, why was I writing the "VxWorks Programming Guide" when I was at ISI in the middle part of 1989? This isn't memory; I have a friggin' copy sitting right here in my office, and I know that I worked there from February to November of 1989--I was in my car leaving work at ISI the day the 1989 Loma Prieta earthquake hit, so it's not like it's easy to forget. Was VxWorks perhaps a joint program between ISI and Wind River prior to the acquisition? Is it possible the pSOS entry contains errors? I don't know where the problem is in the history, but the following are facts: I have a VxWorks document that I wrote, while I was at ISI, in the middle part of 1989. Other than that, I'm open to suggestions.Dougom (talk) 19:02, 30 September 2009 (UTC)

"native" systems such as Unix ??????

Unlike "native" systems such as Unix, VxWorks development is done on a "host" machine running Unix or Windows, cross-compiling target software to run on various "target" CPU architectures.

What nonsense is this? *nix systems can be developed on a host machine and have programs cross compiled to a target machine. This sentence makes it seem like VxWorks is the exclusive embedded OS. —Preceding unsigned comment added by 134.84.0.240 (talk) 19:43, 29 March 2009 (UTC)

²nd this. Crosscompiling can be done in unix/linux/whatever aswell. VxWorks certainly isn't the only OS which is (or can be) cross compiled.

Marketing ?

enhanced C++ features for exception handling and template support

How can an embedded operating system be "enhanced for C++" ?? This sounds like marketing to me. —Preceding unsigned comment added by 140.253.32.116 (talk) 02:22, 23 April 2009 (UTC)