If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#61
|
|||
|
|||
Win32 or Win64
On 5/13/2010 22:35, johnbee wrote:
Just for information: I do not do much word processing, but my wife does. This is the first PC I have had with Office on it, and I am not much impressed, neither is Pat, and we would far rather install our old Lotus Wordpro. Trouble is, it won't work under Windows 7. No doubt the Microsoft screw everybody else's software it is our Operating System policy. They have cut some fonts as well, though they don't cost a lot each. Have you tried to install and/or run it with Windows Vista or XP compatibility mode? You can do it like this: Right-click on it, choose Properties-Compatibility and there you have the option. If you have Windows 7 Professional, Ultimate or Enterprise, you can download and install "Windows XP Mode". This allows you to run older applications that does not run on Windows 7, via Virtual PC, but right on your desktop. http://windows.microsoft.com/en-us/w...indows-xp-mode |
Ads |
#62
|
|||
|
|||
Win32 or Win64
"Kerry Brown" *a*m wrote in message news Thank you for your help! Your post made for interesting reading/thinking! I don't run a "junked-up" computer either. Who needs these 1 TB systems! : ) I was computing before there were "windows"! So was I. Do you know what this does? pip b:new=ald1,ald2 I had to cheat. I never used CP/M. : ) Bill |
#63
|
|||
|
|||
Win32 or Win64
"Bill" wrote in message
... "Kerry Brown" *a*m wrote in message news Thank you for your help! Your post made for interesting reading/thinking! I don't run a "junked-up" computer either. Who needs these 1 TB systems! : ) I was computing before there were "windows"! So was I. Do you know what this does? pip b:new=ald1,ald2 I had to cheat. I never used CP/M. : ) IIRC, "pip" was essentially the copy command in CP/M. So in following the above command, it would appear it would concatenate 2 files in a 3rd new file (new file is both old files combined). The part I can't remember is the a: and b:. Was that used back then to identify floppy drives? Or am I mixing up a DOS convention that wasn't the same? If I'm right about that part, then amend my understanding of the command line to this... Combine the 2 files that are on the a: drive to a new file on the b: drive. |
#64
|
|||
|
|||
Win32 or Win64
"Seth" wrote in message ... "Bill" wrote in message ... "Kerry Brown" *a*m wrote in message news Thank you for your help! Your post made for interesting reading/thinking! I don't run a "junked-up" computer either. Who needs these 1 TB systems! : ) I was computing before there were "windows"! So was I. Do you know what this does? pip b:new=ald1,ald2 I had to cheat. I never used CP/M. : ) IIRC, "pip" was essentially the copy command in CP/M. So in following the above command, it would appear it would concatenate 2 files in a 3rd new file (new file is both old files combined). The part I can't remember is the a: and b:. Was that used back then to identify floppy drives? Or am I mixing up a DOS convention that wasn't the same? If I'm right about that part, then amend my understanding of the command line to this... Combine the 2 files that are on the a: drive to a new file on the b: drive. Yep. And I was using 8" single sided floppies... Chris |
#65
|
|||
|
|||
Win32 or Win64
"Bill" wrote in message ... "Kerry Brown" *a*m wrote in message news Thank you for your help! Your post made for interesting reading/thinking! I don't run a "junked-up" computer either. Who needs these 1 TB systems! : ) I was computing before there were "windows"! So was I. Do you know what this does? pip b:new=ald1,ald2 What percentage of Windows users do you suppose have never run ANY command from the command line? I admit when Windows first came out, I was a ney-sayer--"surely it wouldn't support the complex manipulations I needed to perform fromt the command line"...once in a while, I miss some of my xedit editing commands, but not too often! Bill |
#66
|
|||
|
|||
Win32 or Win64
|
#67
|
|||
|
|||
Win32 or Win64
"Bill" wrote:
What percentage of Windows users do you suppose have never run ANY command from the command line? Perhaps the question could be asking how many users know that you *can* run nontrivial commands from the command line? Or that there are some things you can only do from the command line? I've automated most of the Windows 7 build process at my POE using numerous command-line scripts, plus a few PowerShell scripts and C# applications where the CMD shell doesn't offer the needed function. I take some (good-natured) ribbing for using the old tools, but my response is the same as it's been for years: it does everything we need it to do. M$ designed the "Server 2008 Core" configuration to operate exclusively from the command line: there is no GUI support. One interesting statistic about this is the number of security bulletins that list Server 2008 as an affected system...but then note that Server Core is NOT affected. I admit when Windows first came out, I was a ney-sayer--"surely it wouldn't support the complex manipulations I needed to perform fromt the command line"...once in a while, I miss some of my xedit editing commands, but not too often! If you miss the power of the XEDIT commands, buy a copy of Kevin Kearney's KEDIT application that essentially ports the XEDIT interface to the PC world, using REXX as its macro language. (If you're interested, buy it now. Kevin has stated that he plans to market it only through the end of this year, and support it for another year. I suspect that his potential customer base - i.e., the old VM community - is either already a customer or never will be.) The current version (1.6) runs on both 32-bit and 64-bit Windows 7. www.kedit.com I routinely use the old character-mode KEDIT for DOS program for quick text edits. Like Quicken for DOS (which I still use to keep track of bank and credit card accounts) it does what I want with a minimum of fuss. Joe Morris |
#69
|
|||
|
|||
Win32 or Win64
"Chris Sidener" wrote in message
... "Seth" wrote in message ... "Bill" wrote in message ... "Kerry Brown" *a*m wrote in message news Thank you for your help! Your post made for interesting reading/thinking! I don't run a "junked-up" computer either. Who needs these 1 TB systems! : ) I was computing before there were "windows"! So was I. Do you know what this does? pip b:new=ald1,ald2 I had to cheat. I never used CP/M. : ) IIRC, "pip" was essentially the copy command in CP/M. So in following the above command, it would appear it would concatenate 2 files in a 3rd new file (new file is both old files combined). The part I can't remember is the a: and b:. Was that used back then to identify floppy drives? Or am I mixing up a DOS convention that wasn't the same? If I'm right about that part, then amend my understanding of the command line to this... Combine the 2 files that are on the a: drive to a new file on the b: drive. Yep. And I was using 8" single sided floppies... Yeah, I ditched 8" when I got rid of my Altos multi-user CPU (Altos processing box with 2 Hazelton dumb terminals). |
#70
|
|||
|
|||
Win32 or Win64
On 5/13/2010 6:39 PM, Dennis Pack wrote: In , says... wrote in message ... "Kerry *a*m wrote in message news Thank you for your help! Your post made for interesting reading/thinking! I don't run a "junked-up" computer either. Who needs these 1 TB systems! : ) I was computing before there were "windows"! So was I. Do you know what this does? pip b:new=ald1,ald2 I had to cheat. I never used CP/M. : ) IIRC, "pip" was essentially the copy command in CP/M. So in following the above command, it would appear it would concatenate 2 files in a 3rd new file (new file is both old files combined). The part I can't remember is the a: and b:. Was that used back then to identify floppy drives? Or am I mixing up a DOS convention that wasn't the same? If I'm right about that part, then amend my understanding of the command line to this... Combine the 2 files that are on the a: drive to a new file on the b: drive. Seth: If my memory is correct the a drive was for the 3.5" floppy and the b drive was for the 5.25" floppy. Have a great day. Dennis. We didn't have 3.5" floppies then and some PC's didn't have Hard drives, just the 2 5.25"s. |
#71
|
|||
|
|||
Win32 or Win64
What percentage of Windows users do you suppose have never run ANY command from the command line? The command line is making a big come back in Powershell. Probably not for the casual user but definitely power users will want to be familiar with Powershell. If you manage MS Server OS's it is now required. -- Kerry Brown |
#72
|
|||
|
|||
Win32 or Win64
Kerry Brown wrote:
What percentage of Windows users do you suppose have never run ANY command from the command line? The command line is making a big come back in Powershell. Probably not for the casual user but definitely power users will want to be familiar with Powershell. If you manage MS Server OS's it is now required. PowerShell = ?? http://www.google.com/search?aq=f&so...8&q=powershell |
#73
|
|||
|
|||
Win32 or Win64
On Thu, 13 May 2010 19:39:17 -0400, Dennis Pack
wrote: If my memory is correct the a drive was for the 3.5" floppy and the b drive was for the 5.25" floppy. Have a great day. No. A: and B: have always been for floppies, regardless of size. In their earliest days, PCs only had 5.25" floppy drives and both A: and B: were used for them. After the 3.5" floppy drives became common, you could still have one floppy drive or two floppy drives. If you had one floppy drive, it would be A: and could be either 5.25" or 3.5". If you had two floppy drives, they could both be either 3.5" or 5.25". Or there could be one of each, with either the 5.25" or 3.5" using A: and the other size using B: Ken Blake, Microsoft MVP (Windows Desktop Experience) since 2003 |
#74
|
|||
|
|||
Win32 or Win64
"LouB" wrote in message
... Kerry Brown wrote: What percentage of Windows users do you suppose have never run ANY command from the command line? The command line is making a big come back in Powershell. Probably not for the casual user but definitely power users will want to be familiar with Powershell. If you manage MS Server OS's it is now required. PowerShell = ?? http://www.google.com/search?aq=f&so...8&q=powershell He's talking about this one... http://technet.microsoft.com/en-us/s...owershell.aspx |
#75
|
|||
|
|||
Win32 or Win64
PowerShell = ?? All Programs = Accessories = Windows PowerShell -- Kerry Brown |
Thread Tools | |
Display Modes | Rate This Thread |
|
|