Thread View: comp.os.ms-windows.apps
6 messages
6 total messages
Started by riker
Thu, 07 Jul 1994 04:40
MicroSoft's "Common Applications" and Word For Windows
Author: riker
Date: Thu, 07 Jul 1994 04:40
Date: Thu, 07 Jul 1994 04:40
50 lines
3633 bytes
3633 bytes
Hi. First, please, be kind enough to permit me to get something off my chest: F**k MicroSoft and Bill Gates for their damn arrogance! Thank you for hearing me. I feel better now. On to the questions at hand. (1) I have just installed MS Word for Windows 6.0 (the upgrade version from 2.0, actually). The $&#%@ program insists on installing all the "common" MicroSoft applications (such as spell checker, chart maker, filters, etc.) on the same drive where I have the MS Windows program and system files. This is a big problem for me, because I have my hard drive partitioned into 33 Meg logical drives. Even with DoubleSpace, I am nearly out of room on the D: drive. (There is probably a lot of junk in the system directory that could be deleted, but who the hell knows which DLLs or font files are still needed?!!) Now, I went into WIN.INI, found all references to the common apps, and changed the path to a different drive. Then, of course, I also copied all the program files for the common apps to the new drive and path. (In fact, I placed them in directories with the same path names as they originally had on the D: drive; only now they were on the E: drive, which is also where I have Word for Windows 6 installed.) I then restarted my system, and restarted Windows. The long and short is, Word For Windows could not find the common applications. [I had to copy all the files back to D:, restore WIN.INI to it's original state; then Word for Windows was happy. I was not.] Can anyone tell me how to move the common applications to a different drive, and get MS Word for Windows to recognize them? [P.S. I called MicroSoft tech support. The fellow I spoke to, who was very nice, acknowledged that other people had complained about the same problem. He had no solution to offer.] (2) I appear to have version 6.0, not 6.0a or 6.0b, or whatever the latest release is. I base this on what it says under "About MicroSoft Word" under the Help menu. Does anyone know how I obtain the updated, bug-fixed files. Is there a MicroSoft FTP site, or do I have to call MicroSoft and get updated disks? (3) I have a proposal. How 'bout if 1 million MicroSoft program users put up $1000 each, and buy MicroSoft stock, forming a large enough voting block to make those arrogant SOBs respond to the consumers? Any takers? Thanks in advance for all replies. Steve Oppenheimer
Re: MicroSoft's "Common Applications" and Word For Windows
Author: Jan Gunnar Moe
Date: Thu, 07 Jul 1994 10:26
Date: Thu, 07 Jul 1994 10:26
37 lines
2538 bytes
2538 bytes
I place my reply in public, since it may be of public interest. It also should be corrected in public if not correct. In article <2vg0vc$biq@access3.digex.net> riker@access3.digex.net writes: >Now, I went into WIN.INI, found all references to the common apps, and >changed the path to a different drive. Then, of course, I also copied >all the program files for the common apps to the new drive and path. >The long and short is, Word For Windows could not find the common >applications. I once had a related problem, where W4W 6.0 seemed unable to read my modifications of WIN.INI. The reason? W4W 6.0 (or it may be Windows 3.1 itself, I'm not sure) does not read WIN.INI. Instead it reads another file, named REG.DAT, which is not ASCII. And when you modify WIN.INI, REG.DAT is not updated! What human person could guess this? So what do you do to get REG.DAT updated? You just delete delete the file (REG.DAT). Then, the next time you start Windows, REG.DAT will be regenerated, using your modified WIN.INI. After this treatment, the system should work. At least it did for me (but my problem, as I said, was related to this one, not identical) Implementing automatic updating of REG.DAT after modifying WIN.INI should be very easy, checking, for example, the date of saving WIN.INI. Best Wishes! Jan Gunnar
Re: MicroSoft's "Common Applications" and Word For Windows
Author: Shiva Shenoy
Date: Thu, 07 Jul 1994 14:01
Date: Thu, 07 Jul 1994 14:01
55 lines
3468 bytes
3468 bytes
In <jmo.18.000A713D@mrih.no> jmo@mrih.no (Jan Gunnar Moe) writes: >I place my reply in public, since it may be of public interest. >It also should be corrected in public if not correct. >In article <2vg0vc$biq@access3.digex.net> riker@access3.digex.net writes: >>Now, I went into WIN.INI, found all references to the common apps, and >>changed the path to a different drive. Then, of course, I also copied >>all the program files for the common apps to the new drive and path. >>The long and short is, Word For Windows could not find the common >>applications. >I once had a related problem, where W4W 6.0 seemed unable to read my >modifications of WIN.INI. >The reason? >W4W 6.0 (or it may be Windows 3.1 itself, I'm not sure) does not read >WIN.INI. Instead it reads another file, named REG.DAT, which is not ASCII. >And when you modify WIN.INI, REG.DAT is not updated! >What human person could guess this? >So what do you do to get REG.DAT updated? >You just delete delete the file (REG.DAT). Then, the next time you start >Windows, REG.DAT will be regenerated, using your modified WIN.INI. >After this treatment, the system should work. At least it did for me (but my >problem, as I said, was related to this one, not identical) >Implementing automatic updating of REG.DAT after modifying WIN.INI should be >very easy, checking, for example, the date of saving WIN.INI. >Best Wishes! >Jan Gunnar I am not sure that I would delete the reg.dat file. You may lose a lot of the OLE information in the process. Instead use the filemanager or programmanager's Run command and type in 'regedit /V' (without the quotes). You can now change the paths in the reg.dat file. I have done this on many an occassion. Make a backup copy of your current reg.dat file (in your windows directory) before you modify it. -- ---------------------------------------------------------------------- Shiva Shenoy Aerospace Engineering and Engineering Mechanics shenoy@iastate.edu 2066 Black Engineering Building http://www.public.iastate.edu/~aeem/ Iowa State University Office: (515)294-0092 Ames, Iowa 50011, USA
Re: MicroSoft's "Common Applications" and Word For Windows
Author: Raivo Kilg
Date: Thu, 07 Jul 1994 14:34
Date: Thu, 07 Jul 1994 14:34
31 lines
2583 bytes
2583 bytes
In article <jmo.18.000A713D@mrih.no> jmo@mrih.no (Jan Gunnar Moe) writes: >>Now, I went into WIN.INI, found all references to the common apps, and >>changed the path to a different drive. Then, of course, I also copied >>all the program files for the common apps to the new drive and path. >>The long and short is, Word For Windows could not find the common >>applications. >I once had a related problem, where W4W 6.0 seemed unable to read my >modifications of WIN.INI. >The reason? >W4W 6.0 (or it may be Windows 3.1 itself, I'm not sure) does not read >WIN.INI. Instead it reads another file, named REG.DAT, which is not ASCII. >And when you modify WIN.INI, REG.DAT is not updated! >What human person could guess this? >So what do you do to get REG.DAT updated? >You just delete delete the file (REG.DAT). Then, the next time you start >Windows, REG.DAT will be regenerated, using your modified WIN.INI. NO! Don't delete reg.dat - there can be some vital information for other applications. reg.dat is updated from *.reg, what are ASCII files. You can easily edit them and update reg.dat. Just double-click from File manager on *.reg file and you should see message - "Registration Database updated!". reg files for MSAPPS are in the MSAPPS\* subdirectories. Success!
Re: MicroSoft's "Common Applications" and Word For Windows
Author: Jan Gunnar Moe
Date: Fri, 08 Jul 1994 11:13
Date: Fri, 08 Jul 1994 11:13
27 lines
2442 bytes
2442 bytes
In article <raivo.185.00086114@anal.chem.uva.nl> raivo@anal.chem.uva.nl (Raivo Kilg) writes: >NO! Don't delete reg.dat - there can be some vital information for other >applications. reg.dat is updated from *.reg, what are ASCII files. You can >easily edit them and update reg.dat. Just double-click from File manager on >*.reg file and you should see message - "Registration Database updated!". >reg files for MSAPPS are in the MSAPPS\* subdirectories. Thanks for fast correction! After reading your message, I have tried to find the source for the "delete reg.dat-method". It turned out that the method is described in the book "Take Word for Windows To The Edge by Guy Gallo, ISBN1-56276-079-3, page 403. However on this page, the safer way of using regedit.exe to update reg.dat is described first, as the primary method! I understand your advice against deleting reg.dat this way: If some application put OLE information in REG.DAT without putting the same information in WIN.INI, then this information will be lost when a deleted REG.DAT is reconstructed using the new version of WIN.INI. So I'll use regedit for the future. Thanks to you and the net! Jan Gunnar
Re: MicroSoft's "Common Applications" and Word For Windows
Author: gstark
Date: Tue, 12 Jul 1994 17:33
Date: Tue, 12 Jul 1994 17:33
50 lines
3610 bytes
3610 bytes
In article <raivo.185.00086114@anal.chem.uva.nl>, raivo@anal.chem.uva.nl (Raivo Kilg) writes: > In article <jmo.18.000A713D@mrih.no> jmo@mrih.no (Jan Gunnar Moe) writes: > > >>Now, I went into WIN.INI, found all references to the common apps, and > >>changed the path to a different drive. Then, of course, I also copied > >>all the program files for the common apps to the new drive and path. > > >>The long and short is, Word For Windows could not find the common > >>applications. > > >I once had a related problem, where W4W 6.0 seemed unable to read my > >modifications of WIN.INI. > > >The reason? > > >W4W 6.0 (or it may be Windows 3.1 itself, I'm not sure) does not read > >WIN.INI. Instead it reads another file, named REG.DAT, which is not ASCII. > >And when you modify WIN.INI, REG.DAT is not updated! > >What human person could guess this? > > >So what do you do to get REG.DAT updated? > > >You just delete delete the file (REG.DAT). Then, the next time you start > >Windows, REG.DAT will be regenerated, using your modified WIN.INI. > > NO! Don't delete reg.dat - there can be some vital information for other > applications. reg.dat is updated from *.reg, what are ASCII files. You can > easily edit them and update reg.dat. Just double-click from File manager on > *.reg file and you should see message - "Registration Database updated!". > reg files for MSAPPS are in the MSAPPS\* subdirectories. > I agree! Do not delete - make a copy for safety and then edit using the REGEDIT tool. This tool is found in the system directory and, like SysEdit, is not normally installed as a program item. Pick a group (or make one) and then add New progarm item. Use the Browser and pick RegEdit.exe from the system dir. (if you have not done so, get SysEdit as well). I don't remember whether I put it there or if it is the default, but the command line entry under properties of the RegEdit program item includes the /v parameter mentioned before. The working dir is \windows. Use RegEdit with care!!! The reason it does not come installed is that you can screw up your system in amazing ways. I find it useful when working with jerkoff products like Corel which register themselves as the program to handle too many types of files. I mean, PhotoPaint as the default .pcx or .bmp tool???? Give me a break. Good luck! Gary Starkweather
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads