But that's not related to the bug in xupdate. Xupdate requires the "default printer" registry key to be set. If it is not (like when there are no printers installed), it will exit as soon as it starts up.

d

 

Unless of course your trying to communicate from a python script on a mac running linux.

d

 

i love how the xede is at fault.. not a 50 yr old computer.

 

Who's faulting the Xede? The hardware is top notch. I'm just b*tching about the availability of the communication protocol.

Irrelevant trolling. For these types of applications dated hardware can be much more reliable and functional than the top o' the line Dell space-heater-o-matic.

That's still no execuse to run windows 95/8 though ... *grumble* frickin' dos kernel *gumble*...

cheers
d

 

If you have a "print to file" printer, you could set it as the default printer, that way you alway have a "printer" available for the application.

 

Yeah, that was my first post. "install the adobe postscript printer driver".

It's all good.



d

 

I'm gonna try another laptop today, but I'll go back to mine to do Xmap.

Why not use the 98 machine? I used it on both my corvettes with no problems, and until this problem used it on my Evo8. The programs I'm running on it are tiny and not all that complicated that 98 can't support them. I have a wireless NIC card that I can use to transfer stuff to and from my desktop and that's it. No other programs needed. Sometimes the best solutions are the simplest ones.

Sam

 

And, since I own a business in Redmond I pay lower taxes thanks to MS. Move over a couple cities and it increases, they're good for more than just software and Xboxes.

Sam

 

Sorry. That was some irrelevant trolling of my own. Here's what was going through my mind:

Windows 95/98/98se/me are the last descendants of the msdos os base. In otherwords, their kernel is based on windows 3.11 which was based on the not-so-networked windows 3.0 and _that_ was based on the old msdos 6.2 kernel.

I worked on device drivers several years back and I have a laundry list of things that bug me about the msdos legacy. It mostly stems from the fact that protected memory didn't work the way it should (if at all) and the inability to get ahold of fine grain timers. Win2k and xp really do seem (I haven't investigated thoroughly) better sorted. They're based off the NT kernel which was written by smart people that microsoft hired from DEC (sort of).

Of course for a simple application like xupdate, none of this matters. Someday I'll learn to keep my mouth shut.

d

 

For this type of application, Windows 98 is actually a pretty good platform. Obviously Win2K or XP Pro would be better, but that requires too large of a footprint to run well on older hardware. NT 4 would be great, but IMO the NT 4 hyperterm sux and com ports can be a major PITA... that's my irrelevant $.02

l8r)

 

I was trying to get at that earlier, but I can't defend windows without getting sidetracked. . Sure the older win32 footprint works nicer, but imagine how nice a it would run on a bsd variant.

Holy hijacked thread batman.

d

 

Okay, V3 is on the XEDE now so the discussion can be over. Thanks for all the help (to those of you who offered actual help) but I did go the route of using another PC to install Xupdate.

According to Dustin the Port selection interface that he sees in Xupdate is identical to that in Xmap, not so in my case, so the argument that the problem was OS or machine specific does hold water.

I can still use Xmap on the Stinkpad to interface with the XEDE so all's well that ends well.

Sam