Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: Windows 95
- To: tlug@example.com
- Subject: Re: Windows 95
- From: cybernet@example.com
- Date: Sat, 30 Dec 1995 14:34:52 GMT
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
To Steve Turnbull: Well, I have heard about all this problems with the support, but I am currently talking about the practical things only. I did the installation of 95 approximately for 40 machines (both Japanese ad US versions) and I did problems but finally it always was caused by unreliable DMA controller or hardware problem or IO conflict. OK, I've never worked with more than 2 years old BIOSes, but the major problems were with Plug-n-Play or better Plug-and-Pray Systems.ASUSTeK Motherboards with Triton Chipset for instance have trouble with Sound Blaster under Windows (3.1 as well) that is caused by Videocards or their drivers. It was reported by ASUS people. MACH64 is fine, MGA needs new drivers, Cirrus Logics is bad forever, ET4000/W32 is OK. Other problem is with EIDE controllers. If you are using integrated into mother board controllers, you are more or less safe, but with IDE PCI paddle cards you are on your own. All this has nothing to do with the 95, WIN3.1 is also not working. Second. There is a good chance that if you have your system up and running Windows 3.1, loaded with software that looks suspicious in terms of compatibility with 95, after installation of Windows 95 at the same subdirectory, everything will continue to breathe. I did some weird experiments with cyrillic drivers, and video capture cards. Even EEPROM programmer - add-on card, with DOS-based software that writes directly to hardware, was working, at least from the command prompt. About OS coexistents: Sorry never tried OS2, but at my home PC I have Linux, Win95 and Windows NT running almost without any problems. Actually there are problems, but with Windows NT: because I am using old AHA1540 and CMD PCI IDE Card, the last one being recognized by the system as SCSI adapter, so my HP SCSI HDD is always considered by Windows NT as C-Drive, so setup was not straightforward. to: Norihide Kise Basically there is no need to use separate partition for Windows95 and DOS/WIN3.1 You can just install it to separate subdirectories and they will coexists. Older DOS probably will be gone but it should not be a problem. US version of Windows 95 (or may be it was beta) had the option "boot the previous version of DOS", in Japanese version this option is not here anymore or needs some work around - I don't know. As to partitioning - the best way is to make a partition by OS that will be installed on it. Beware though. Yuri.
- Follow-Ups:
- Re: Windows 95
- From: Norihide Kise <s100234@example.com>
Home | Main Index | Thread Index
- Prev by Date: Windows 95
- Next by Date: Re: tlug-digest V1 #98
- Prev by thread: Windows 95
- Next by thread: Re: Windows 95
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links