- Joined
- Jul 23, 2012
- Messages
- 1,899
- Reaction score
- 873
Ain't gonna happen.Windows 10 SUX! Bring back Windows 7!
Yeah, I know. Win 7 was the last good OS. Maybe it's time to look at Linux or <gulp> Apple.Ain't gonna happen.
I'll say it again - Ubuntu Linux - It's free, clean, streamlined, continually updated, fast as hell, you never have to worry about a virus, and you don't wake up to stupid pictures on your screen.
You can use it out of the box, or learn more about it and it is twice as powerful as windows.
It is a tool, not a "Yay we're Microsoft, look at us" platform.
I have tried multiple variants of Linux, including Ubuntu.My laptop that I used for rocketry, Lenovo Thinkpad running XP finally died, well XP did. Only wanted to start in safe mode and now not even that. The Linux option has me intrigued…
My internet connection is two soup cans and a piece of string.
Since I am planning to install Linux on an old machine for use in my workshop (for programming model trains and possibly running a 3D printer - someday) can you elaborate on what kind of tinkering might be required "under the hood"? I am/was an electrical engineer, so tinkering at most levels doesn't worry me, but I'm curious what it might entail, what learning curves I might face, and how time consuming they might be.I've used Ubuntu off and on for years and always enjoyed it. But it absolutely takes tinkering from time to time (more so than the traditional alternatives) and it's just not worth it to me most of the time. And definitely not something I'd recommend to a user that doesn't feel comfortable opening the hood from time to time as needed.
If you have standard "stuff" (video card, network card, drive controller, etc.) then it'll work out of the box with most standard modern distros of Linux (Mint, Ubuntu, CentOS(r.i.p) etc.) If you have a funky, off-brand SAS RAID controller that was given to you from 2005 that you think might work.....it might if you're willing to work for it. If you have bleeding edge hardware (brand-new 2.5G network card that's been on the market a week) you may have to manually install drivers but a quick Google search normally finds a fix. If you're wanting to get a DOS program written in 1987 working in a virtual environment with Linux being the host OS, you can do that too if again you do a Google search and follow the dozen how-tos that are out there. If you heard about Gentoo and want to compile and build everything from source code, its possible and you'll learn ALOT but you'll be spending the next month learning before you have a working system.Since I am planning to install Linux on an old machine for use in my workshop (for programming model trains and possibly running a 3D printer - someday) can you elaborate on what kind of tinkering might be required "under the hood"? I am/was an electrical engineer, so tinkering at most levels doesn't worry me, but I'm curious what it might entail, what learning curves I might face, and how time consuming they might be.
Thanks., I'm not expecting to do anything exotic, bleeding edge, ancient, or rare so that helps. Searching for the occasional driver seems pretty normal even for Windows. Especially for those of us who were using Windows ten or twenty years ago.If you have standard "stuff" (video card, network card, drive controller, etc.) then it'll work out of the box with most standard modern distros of Linux (Mint, Ubuntu, CentOS(r.i.p) etc.) If you have a funky, off-brand SAS RAID controller that was given to you from 2005 that you think might work.....it might if you're willing to work for it. If you have bleeding edge hardware (brand-new 2.5G network card that's been on the market a week) you may have to manually install drivers but a quick Google search normally finds a fix. If you're wanting to get a DOS program written in 1987 working in a virtual environment with Linux being the host OS, you can do that too if again you do a Google search and follow the dozen how-tos that are out there. If you heard about Gentoo and want to compile and build everything from source code, its possible and you'll learn ALOT but you'll be spending the next month learning before you have a working system.
Anything you want to do, someone else has already done it and written a how-to that you have to follow. Just have to decide how much your time and effort is worth.
If you're wanting to get a DOS program written in 1987 working in a virtual environment with Linux being the host OS, you can do that too if again you do a Google search and follow the dozen how-tos that are out there.
DOSBox. I know it has a fully implemented MS-DOS 5 shell and I think it has a 6.2 as well. I think WINE could work too. You could also fireup ProxMox and install a full copy of MS-DOS 6.22 and then it isn't an emulation or a re-implementation but a true MS-DOS 6.22 shell.Ok, I was hoping to implement a DOS command interpreter but I need a shell that has all the DOS 6.2 Intrinsic commands supported so that I truly have a seamless DOS environment.
Does that work?
Just kidding, I agree with your post. You can do most of what you want with the commensurate amount of effort.
I'll beat you about the head with a clue-by-four. MS BOB was the 3rd worst thing ever inflicted upon us by MS. Clippy and Windows ME are worse.What if I want to run Bob in Wine on Ubuntu?
DOSBox. I know it has a fully implemented MS-DOS 5 shell and I think it has a 6.2 as well. I think WINE could work too. You could also fireup ProxMox and install a full copy of MS-DOS 6.22 and then it isn't an emulation or a re-implementation but a true MS-DOS 6.22 shell.
1000 ways to skin a cat when it comes to Linux.
Tink Tink Tink...I'll beat you about the head with a clue-by-four. MS BOB was the 3rd worst thing ever inflicted upon us by MS. Clippy and Windows ME are worse.
Enter your email address to join: