CompuServe Thread

#Adaptec and Imagine

10 messages in this thread
#86467From: David HofmannJul 18, 1994 2:32 PM
Hi Imagine users, Has anyone here an Adaptec VLB SCSI Controller? I just bought one with a 1 gb IBM HD. Since I have build it in Imagine crashes fequently. When I put it out everything works fine. Any ideas that might help are appreciated. -David
#86470From: Marc ReinigJul 18, 1994 3:04 PM
David, Some questions: 1. Did you have a CD driver loaded before on another controller, or have you just loaded it with this one? 2. Does it work with other programs and just not with Imagine? 3. Did you just add EMM386 or another memory manager to be able to LOADHIGH the drivers? 4. What version of DOS are you using? 5. What are the settings on your EMM386 or other memory manager? -Marco
#86536From: David HofmannJul 19, 1994 3:52 PM
Hi Marc, thanks for your reply >> 1. Did you have a CD driver loaded before on another controller, or >> have you just loaded it with this one? Yes I have a CD-ROM driver and also a second one so that the disk cache software can cache the CD-ROM, too. But when I "clean-boot" there is no driver except the mouse driver. >> 2. Does it work with other programs and just not with Imagine? It also causes trouble with OzCIS when the controller is in, it's not only Imagine. Unfortunately OzCIS and Imagine are the two most important programs I have. >> 3. Did you just add EMM386 or another memory manager to be able to >> LOADHIGH the drivers? I have DOS 6 and use 386Max 7. But I also tried to boot without anything (except a mouse driver) and the problems were the same. >> 5. What are the settings on your EMM386 or other memory manager? I don't think that the mem manager is the problem. Even when I boot without it it still crashes. With some switches I can set different I/O ports for the controller. I will have to try all of them and see if it helps. Maybe that's the problem. I don't know much about all these IRQs, I/O ports, memory stuff 🙁 but then I'm not a developer. -David I just started to change the I/O port addresses one by one. I tried the next address, booted and started Imagine. So far no crash! Maybe I found the right address right away.
#86552From: Marc ReinigJul 19, 1994 8:05 PM
David, The fact that your adapter causes problems with OZCIS is a strong indication that you have either address or interrupt problems or both. I think you are on the track of the solution. -Marco
#86557From: Troy BarlowJul 19, 1994 8:58 PM
David, You may also want to make sure there are no BIOS conflicts with the Adaptec card. Check your CMOS settings and make sure you are not stepping on memory with shadow ram (that may be used by a ROM on the Adaptec) or other CMOS settings (i.e. if you have AMI BIOS, there are a lot of settings in CMOS that can cause problems). -Troy
#86633From: David HofmannJul 20, 1994 1:56 PM
Troy, thanks for your help. After changing the I/O port address of the adapter I haven't had any chrashes any more. Looks like it works now. -David
#86622From: Peter GreciJul 20, 1994 12:15 PM
Glad you got yer machine working again David…..
#86650From: David HofmannJul 20, 1994 6:59 PM
>> Glad you got yer machine working again David….. Yes, I felt really stupid having bought hardware for $1100 only to find out that it won't work with my favorite software. But now everything works fine again and it like christmas and birthday at the same time 🙂 -David
#86528From: SyndesisJul 19, 1994 11:58 AM
To get my Ultrastor 34F to work properly with QEMM, I needed to add a special patch in CONFIG.SYS before QEMM. In other words, I think there are known conflicts between some high-speed VLB SCSI adapters and other memory managers… given that Impulse wrote their own memory manager, it's going to be tough to find the problem, I'd guess.
#86606From: David HofmannJul 20, 1994 7:13 AM
Hi, thanks for your reply. I know of the problem that 386Max has with the Adaptec controller. I had to add NOIOWRAP in the profile file in order to get the new HD (and the controller) to run at all. Fortunately I found the problem. I had to change the I/O port address of the adapter to get rid of the problem. It works fine now. thanks anyway -David