News for hackers. Stuff that matters.
Re:The Art of Not Working at Work by Natsu on Wednesday November 05, 2014 @12:20AM (#8560617)
I worked with DOS as recently as 6 years ago. It's actually not all that bad, assuming you've got them on a network. We had a Novell server and they all mounted a network share on that at boot. From there, backups (and restores) were just a simple xcopy script. I ran a script to create 'flag' files to trigger the backup on reboot and the machines were shut down every night, so it was quite simple to manage.

I was able to deploy updates via a similar mechanism. There was a network script called from autoexec.bat. I would make a few changes to have it pull in the new updates from the network, then tell them to reboot at their convenience. So I almost never had to leave my desk to deal with them, except for a restore from backup.

Re:The Art of Not Working at Work by marktangotango on Wednesday November 05, 2014 @05:55AM (#8561278)
How did one do network programming in dos? Did it have a tcp/ip stack and winsock.h funtions or equivalent? And threading? Did you use Djgpp? I've always wondered about that.

Edit: browsed the DJGPP website and found answers, there are libs available.

Re:The Art of Not Working at Work by pjc50 on Wednesday November 05, 2014 @06:23AM (#8561346)
You didn't, mostly.

In DOS times you only had one core, so there was no particular necessity for multithreading. Network card drivers were available using the NDIS standard: http://www.freedos.org/wiki/index.php/Networking_FreeDOS_-_N...

DOS games tended to roll their own protocol on top of the raw packet drivers. This is why they were often LAN-only. Generally in the DOS era you didn't have Internet; it existed, but wasn't widely deployed.

DJGPP got some use (see the PCGPE as well), but professional game development tended to use Watcom: http://www.openwatcom.org/index.php/Project_History

Re:The Art of Not Working at Work by Natsu on Wednesday November 05, 2014 @03:23PM (#8564051)
We didn't do anything like network programming where I worked. We just copied files on and off of network shares with batch files or such and let the Novell drivers handle the network.

So you'd download the day's schedule or updates by copying the file off the network and use a few primitive means of coordinating things like using 'flag' files for signaling and then if exists xxx / echo foo > do_bckup.txt type things in your batch files.

It's very primitive, but most things were at least doable and you could always write small programs to extend your scripts if need be.

Re:The Art of Not Working at Work by Jedd on Wednesday November 05, 2014 @06:16AM (#8561322)
winsock may have come a bit later ;)

Read up on the Wollongong TCP stack - very much an MS-DOS stack that I have mixed memories (some fond, some horrendous) of.