Yes I realize that :) not sure if I'm going to install MS-DOS 6.22 or windows 95.
Re: Thin client PC to run MS-DOS
By: Denn to Lordwoodoo on Mon Nov 24 2025 01:03 pm
Well, I would suggest to install both, and even Windows 3.1 on the MSDOS partition is a cool thing. I will explain why later. It is always good to have a pure MSDOS. In that case, you need to part the hard drive in 2 partitions. One for MSDOS, 2 gb max, and the second to install Windows 95. See the max capacity limit for Windows 95, and if the hard drive have more space after that, you will have more space to create one more partition for data for exemple: games or software, etc.. for Windows 95. A very important thing is: you need to create 2 primary partitions to be able to boot both!! Before doing the installs. FDISK or Partition Manager will do the trick using a floppy drive or a CDRom device.
Installing Win 3.1 on the MSDOS partition does not affect the previous MSDOS installed, and its cool if you want to boot Win 3.1 and use MSDOS in windowed mode over it. You can take notes with notepad, for exemple playing Zork.. have multiple MSDOS windows opened, etc.. Really cool!
I'm leaning towards just installing DOS 6.22. I Remember when Windows 3.0 came out, i bought it and then I upgraded to 3.1, never really liked those 2 versions, they were basically DOS shells, in dos I used a program called xtree.
After Windows 3.0 came out, I think some programs came out that were specifically for Windows 3.x, so you basically had to use Windows to run the
Nightfox wrote to Denn <=-
After Windows 3.0 came out, I think some programs came out that were specifically for Windows 3.x, so you basically had to use Windows to
run them. I think especially things like graphical & drawing tools,
word processors, etc. moved toward Windows because (I think) drawing programs were probably easier to develop for Windows 3.x than for DOS,
and with word processors, you could get WYSIWYG interfaces, so it was a lot easier to create documents just as they'd appear when you print
them, compared to DOS software.
I think Xtree was one of the most popular DOS utilities that was available at the time..
After Windows 3.0 came out, I think some programs came out that were specifically for Windows 3.x, so you basically had to use Windows to run them. I think especially things like graphical & drawing tools, word
I will look into Xtree. Dont know it.
I think Xtree was one of the most popular DOS utilities that was available at the time..
To me, it was a Window manager before we had window managers. For a
time, the last line of my autoexec was to run Xtree.
today, that and QEdit (file editor) and a LIST clone called LOOK.COM
I know it was probably my most-used utility back in my DOS days...
Man, so many people were all about xtree gold..
I didn't know any DOS command shell had tab completion.. I had even used 4DOS sometimes..
today, that and QEdit (file editor) and a LIST clone called LOOK.COM
What features does 'look' bring?
Most apps put themselves in the same directory name as the executable. A crafty sort would write a batch file called go.bat that read:
phigan wrote to poindexter FORTRAN <=-
Most apps put themselves in the same directory name as the executable. A crafty sort would write a batch file called go.bat that read:
I did stuff like that for a bit and then the OCD in me got pissed at
all the extra files laying about so I deleted them.
Subject: Re: Thin client PC to run MS-DOS
@MSGID: <693484C2.202.dove.hardware@realitycheckbbs.org>
@REPLY: <693370AB.1247.dove-hwswhelp@tacopronto.bbs.io>
@TZ: 41e0
phigan wrote to poindexter FORTRAN <=-
Most apps put themselves in the same directory name as the executable. A crafty sort would write a batch file called go.bat that read:
I did stuff like that for a bit and then the OCD in me got pissed at all the extra files laying about so I deleted them.
You'd only need one batch file - using command line variables, it'd take
the first argument on the command line, change directory to the
directory named %1, then run the command %1.
go, "go procomm" would be the same as running:
cd \procomm
procomm
type in "go telix" and it'd run:
cd \telix
telix
You'd only need one batch file - using command line variables, it'd take
Digital Man wrote to poindexter FORTRAN <=-
Or just put \procomm and \telix in your search PATH. Most of those programs were smart enough to be able to find their config/data files based on argv[0] and didn't really need the current working directory
to be "their" directory upon invocation. --
phigan wrote to poindexter FORTRAN <=-
True that, but didn't think about it at the time. Probably would've
made me a lazier typer anyway ;). These days while on video calls
working with people, they're like "onoez! we can't copy/paste this long path into this web based terminal!" and before they're even done complaining about it, I've typed it in and gone on to the next step of whatever we're doing.
| Sysop: | John F Kennedy |
|---|---|
| Location: | Quebec, Canada |
| Users: | 20 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 149:09:55 |
| Calls: | 218 |
| Calls today: | 218 |
| Messages: | 1,582 |
| Posted today: | 2 |