CompuServe Thread

#Problems with June Issue

9 messages in this thread
#52785From: Linda L. RosenbaumJul 14, 1993 10:28 PM
I am having several problems since installing the "upgrades" that came with the June issue of Nautilus. First let me describe my system. I am using a 486-33 with 16 meg of RAM, Diamond Stealth video card with most recent drivers in 1024x768x256, Pro Audio Studio 16 sound card with most recent drivers, DOS 6.0, Windows 3.1, and Norton Desktop for Windows 2.2. If you need other info about my hardware and/or software, let me know. I installed all the software upgrades in the June issue (Nautilus software version 1.78, Video for Windows update, and Quicktime for Windows). I now have the following problems: 1) When certain parts of the issue with sound are played, the volume on my sound card is raised to maximum. I think it is the wave driver that is being affected but not positive. I have to manually change it back with the mixer program for my sound card. I know others have had the same thing happen with other sound cards. 2) I now sometimes get system errors that in effect say that my CD-ROM drive can't be accessed. I got this recently when actually using a CD in the drive (MacMillan's Dictionary for Children). I would hit the retry button and the program would continue okay. This happened multiple times. I got the error last night while doing something in windows with an audio CD in the drive. I looked in my win.ini file and several others to see what might be causing this but was unsuccessful. I usually am able to hit cancel and then whatever I was trying to do proceeds okay. But these system errors shouldn't be ocurring, didn't before the June issue of Nautilus arrived, and are extremely annoying. 3) After using the June Nautilus CD, if I try to run Media Player, I get a GPF that refers to QTNOTIFY, and when I hit the okay button, I am dumped back to the DOS prompt. I can run Media Player just fine as long as I don't run Nautilus. This is a very bad problem. Last night when this happened the first error message was the one mentioned above about not being able to access the CD-ROM drive and then the GPF message came up. Have any or all of the above problems been reported? Any suggestions on cures, particularly for the last one? Thanks! Linda
#52807From: Ron WodaskiJul 15, 1993 11:39 AM
I have seen similar problems on machines where the CD-ROM drive was beginning to malfunction; it is worse on some disks than others. After a time, all disk may become hard to read. Often, oddly enough, an upgrade of the ROM chip will solve the problem. If not, the drive needs to be serviced. I can't, of course, say for sure that this is *your* problem. <g> What kind of CD-ROM drive do you have in your system? Does it connect to the PAS? You could also check to loose cable connections. ROn
#52864From: Linda L. RosenbaumJul 15, 1993 10:02 PM
Ron, Thanks for the reply but I don't really think it is the CD-ROM drive (at least not the GPF with Media Player nor the problem with volume of the sound card). And the other system error happens at random times (ie I can't figure out the pattern yet) and many times when I am doing nothing with the CD drive itself. All other CD's have been functioning just fine as well as audio CD's. Anyway I can't believe I forget to post what drive I use <g>. I use the Texel DM 3024 and do indeed have it connected to the Studio 16 sound card. I have the ROM upgrade for multisession but don't know for sure if that is indeed the latest. And this problem didn't start until after I installed the June issue of Nautilus. Of course that could be coincidence. I anxiously await some feedback from Nautilus. If you have any other ideas or things I can check please let me know. I will try almost anything… Linda
#52867From: Ron WodaskiJul 15, 1993 11:43 PM
Well, I had the exact same problems you described with the Texel drives, and they didn't go away until I got the 1.09 version of the ROM chip. Ron
#52932From: Linda L. RosenbaumJul 16, 1993 9:21 PM
Ron, >>Well, I had the exact same problems you described with the Texel drives, and they didn't go away until I got the 1.09 version of the ROM chip.<< Hmmmm…. Is that the version that comes with the multisession upgrade or an even newer one? If newer I sure can try calling Texel to see if I can get it. And I don't recall how to tell what version one does have and don't remember if it displays on boot up (I don't usually turn the computer on in the morning but rather my husband does). Just got a response from Nautilus and tried Media Player after running Nautilus. Worked just fine right now. I forgot to mention it in yesterday's post but we had to open up the computer case last night (we are having problems with our tape backup unit) so while we in the neighborhood I had my husband check the connection from the Texel to the Studio 16. Hmmmm… Anyway thanks for the help and I haven't gotten any of the random system errors about not being able to access the CD-ROM drive in a few days. Keeping my fingers and toes crossed… Linda
#52936From: Ron WodaskiJul 17, 1993 12:11 AM
I had two Texel drives. One had the symptoms you described, and they got rapidly worse; I sent it back to be replaced. The second drive had minor symptoms that went away entirely with the upgrade. In addition to upgrading to 1.09 of the firmware, i also upgraded my Trantor SCSI drivers to 3.04; apparently, this is something you must do if you have a Trantor SCSI card — and that may not be obvious unless you observe the boot-time messages, as Trantor is responsible for several OEM cards as well, such as the Pro Audio Spectrum 16. If you have a PAS (I don't recall if you said…), you should download the latest SCSI driver from the MULTIVEN forum, I believe that Media Vision is in LIB 12. Good luck! Ron
#52926From: Margo RiedelJul 16, 1993 8:19 PM
Hi Linda! QuickTime for Windows movies are very new to the marketplace. A few subscribers have reported intermittent problems with the sound volume automatically rising to the maximum. We have passed this onto Apple so that the problem can be resolved at a future time. As far as Media Player not working since you installed the June issue, we tested ours and have no problems with it. Exactly what file were you trying to run when you got the QTNOTIFY GPF error? Was it a QuickTime for Windows (.MOV) file? You might want to check the QTWNOTIFY file which is located in the Windows System directory on your hard disk. The size of the file should be 4080. If your file size doesn't match or is non-existent, please reinstall the QuickTime for Windows driver. To do this go into the Windows File Manager to the root of your CD ROM drive and highlight the setup directory and click twice on the setup.exe file to rerun the setup. Then add the QTW driver. If you still have problems, you might consider lowering the resolution of your video card drivers to 640×480. Also, please advise if you are using the DoubleSpace feature of DOS 6.0. Please let me know if these suggestions help you. I'm looking forward to your reply. Thanks for your support of Nautilus. Karin Gall Nautilus Technical Support
#52933From: Linda L. RosenbaumJul 16, 1993 9:21 PM
Karin, >>Hi Linda! QuickTime for Windows movies are very new to the marketplace. A few subscribers have reported intermittent problems with the sound volume automatically rising to the maximum.<< Thanks! I will look forward to an updated driver in a future issue <g>. Anyway it is easy to fix with the software mixer program for my sound card. >>As far as Media Player not working since you installed the June issue, we tested ours and have no problems with it. Exactly what file were you trying to run when you got the QTNOTIFY GPF error? Was it a QuickTime for Windows (.MOV) file?<< Actually I wasn't getting far enough to run anything. I would try to open up Media Player, then got a system error about not being able to access the CD-ROM drive, and then got the GPF about QTNOTIFY after responding cancel on the prior message. After an okay to the GPF, I was dumped back to the DOS prompt. So in effect I wasn't getting Media Player to even load successfully to even try to run anything. >>You might want to check the QTWNOTIFY file which is located in the Windows System directory on your hard disk. The size of the file should be 4080.<< It checks out okay. >>If you still have problems, you might consider lowering the resolution of your video card drivers to 640×480.<< Grrr. I don't usually ever load that driver. I have a 17" monitor and have yet to ever try any of the various versions of the Diamond Stealth drivers in 640×480. And given that these are Diamond drivers its highly unlikely that a lowere resolution driver will work any better than a higher resolution driver <g>. >>Also, please advise if you are using the DoubleSpace feature of DOS 6.0.<< Yes I do. The partition that has the Nautilus subdirectory is DoubleSpaced but the partition with windows and all of its subdirectories is not. Now for the good news. Before responding to your message I did try once again and this time I had no problem. I am very baffled and most definitely had the problem prior to my message of the other day. And this had been repeated several times over the course of the last few days. About the only thing I have done in the last day is check the connection of the cable for the CD-ROM drive to the sound card (I run the CD-ROM drive off the SCSI interface of the Studio 16 sound card). Very weird but I am glad that all seems to be back to normal again. I hope to be using the June isue some more this weekend and will let you know if the problem reappears. While I have your attention I was wondering if the July issue will be going out this week. And I will be changing video cards very shortly. I hope to run normally in 1024x768x65000 colors. Can Nautilus run if the drivers are good? Or will it only run in 16 color or 256 color? If it should be able to run and I do have problems I will let the company know about them. But if it shouldn't be able to do so… Thanks again! Linda
#52957From: Ron WodaskiJul 17, 1993 1:24 PM
Linda – I use the ATI Ultra Pro at 1024×768 at 65,000 colors routinely with no problems. Ron