CompuServe Thread

#MS Bookshelf

9 messages in this thread
#20733From: Scott MitchumApr 27, 1992 10:35 PM
I'm having trouble getting the Microsoft Bookshelf to finish loading itself into Windows. I've got the SoundBlaster Pro board with the Creative Sounds upgrade kit and internal CDROM drive. Everything else seems to work great, but when I Run the SETUP from the ProgManager, it stops and says Fatal Error writing to the Setup.ini file in the windows\system subdir. It always stops at the CloseFontProgress part, whatever that is! Does anyone have an idea or help? I can still access the Bookshelf programs, but I have to run the viewer from the ProgMan window. That's a real pain, and for this much money the dang thing should work right, right? Any help would be greatly appreciated.
#20742From: David BakerApr 28, 1992 5:24 AM
Sorry, no help, but I can confirm that I have exactly the same problem so we are both doing something wrong or there is a fault in the setup process. I hope we find out as it is a hassle.
#20804From: Scott MitchumApr 29, 1992 10:10 PM
Thanks for your answer. I've just went ahead and put the win version with the multimedia back on because that's the only way I can get the soundblaster pro board and programs to work right. I've heard that this version of win is about 3.05 or so. The strange thing is that I can still use the True Type fonts from 3.1! Now why is that? Very strange. But boy is it nice to play a CD while I'm working without getting up and changing discs or tapes every little bit. Thanks again and I'll let you know if I figure this out
#20745From: John HaysApr 28, 1992 7:26 AM
Scott, From the info I've seen this problem is usually cause by too big a system.ini file for the process. If this is a file size limitation problem, it can be solved by either: 1) deleting all the comment and space lines in your system.ini file or 2) creating a new minimal system.ini file, installing MS Bookshelf, and then copying the needed parts to your original system.ini file. If you are going to try either of these methods, make sure you have good copies of your INI files stashed away before you start. I think I remember something about this in the MSKB, so you might want to look there also. They do also support it in MSAPPS. Hope this helps, Jphn
#20805From: Scott MitchumApr 29, 1992 10:13 PM
Thanks for your help, John. I tried messing with the ini files once before and ended up redoing the whole thing. Some of my friends are still laughing about that one, so I'll be sure and make backups this time. My particular problem seemed to be writing to the setup.inf file, but with win who knows what effects what else! Thanks again Scott
#20820From: John HaysApr 30, 1992 5:54 AM
Scott, Glad I could help. BTW, there is a person with MS Tech Support, named Harry Emil, usually found in the MSAPPS Forum, that seems very good at this sort of thing. You may want to give him a holler if you continue to have problems. Good Luck, John
#20762From: Rick LaBancaApr 28, 1992 5:42 PM
If you are using 3.1 windows, it is a known bug. If you call microsoft, they will send you a free update. Rick
#20806From: Scott MitchumApr 29, 1992 10:14 PM
Thanks a great deal, Rick. I'll call them tomorrow and ask what the deal is. If they ever get this stuff working correctly, it may take all the fun out of computers! Thanks again Scott
#20953From: Roger InmanMay 4, 1992 3:05 AM
Scott, I bought the SB Pro and internal CD kit like you. Like you, I had the same, exact problems with MS Bookshelf. I called Creative Labs who said that I needed their new drive for 3.1 Windows. I downloaded that and it fixed some of my problems but Bookshelf install still hung in the same place. I finally installed it myself. Took about two hours finding the right *.MVB and *.ICO files. However, it now works great and sounds great. It is very impressive. I have the SB Pro piped in to my stereo. Super. Even though the new drivers fixed some things, they made others worse. For instance, some of the *.wav and *.mid files that I could play before don't work now. I think that the CDs we got with the SB package are probably outdated and won't work with the new drivers. Anyway, installing the SB package has been quite an ordeal but worth the effort. Let's keep in touch. I think we can help one another. The manufacturers are of limited help and are hard to contact. I'll be away from the computer until the 8th. Let us know how you are progressing. Roger