Win3x.Org

Windows & DOS Community

CD de restauration - Gateway Solo 2150/2550/9300 [fr]

Répondre   Page 1 sur 1  [ 8 messages ]
Auteur Message
KeetKhat
Sujet du message : CD de restauration - Gateway Solo 2150/2550/9300 [fr]
Publié : 15 févr. 2017 18:51
Membre inscrit
Avatar de l’utilisateur
Hors-ligne
 
Messages : 1737
Inscription : 27 mai 2009 14:04
PC Rétro : IBM ThinkPad 380ED, Windows 95
 
CD de restauration - Gateway Solo 2150/2550/9300

Description

CD de restauration en [fr] pour les PC portable Solo 2150/2550/9300, ils permettent de restaurer Windows 95, 98 (Sous possession des disques originaux), 3.1, 2000 et NT (3.51/4.0) (Installation manuelle)

Mettez le CD "Solo System CD" dans votre lecteur et suivez les instructions, une fois Windows installé lancez l'autorun du CD pour installer les pilotes plus plus courants de votre PC Gateway.

Téléchargements
[fr] [cdrom]x1 Solo System CD (Principaux pilotes) (398.7 MB) Hits : 26 [win] 9x & NT 4.0 & 2k
[fr] [cdrom]x1 Sytem CD Version 2.1 (pilotes et fonds d'écran) (294.1 MB) Hits : 28 [win] 3.x & NT 3.51+ & 9x


Dernière modification par michel le 24 mars 2017 00:44, modifié 3 fois.

Haut
Profil Citer
Big Monstro
Sujet du message : Re: [Propose] CD de restauration - Gateway Solo 2150/2550/9300
Publié : 22 mars 2017 21:58
Administrateur
Avatar de l’utilisateur
En ligne
 
Messages : 2897
Inscription : 27 juin 2003 15:15
PC Rétro : 80486 DX2/66, MS-DOS & Windows 95
 
Citation :
permettent de restaurer Windows 95, 98 (Sous possession des disques originaux) (...) Mettez le CD "Solo System CD" dans votre lecteur et suivez les instructions, une fois Windows installé lancez l'autorun du CD pour installer les pilotes plus plus courants de votre PC Gateway. (...) [fr] CD-ROM d'amorçage "Solo System CD" + Principaux pilotes (95/98/NT 4.0/2000)
Si je comprends bien, on démarre l'ordinateur avec le premier CD et on change de disque en cours de route pour installer Windows ?

Quel intérêt d'amorcer le PC avec ce disque ? On pourrait très bien installer Windows normalement et ensuite installer les pilotes, non ?


Haut
Profil Citer
KeetKhat
Sujet du message : Re: [Propose] CD de restauration - Gateway Solo 2150/2550/9300
Publié : 22 mars 2017 22:16
Membre inscrit
Avatar de l’utilisateur
Hors-ligne
 
Messages : 1737
Inscription : 27 mai 2009 14:04
PC Rétro : IBM ThinkPad 380ED, Windows 95
 
Ça sert à automatiser l'installation, le CD se charge de formater le disque dur, de copier les fichiers du CD de Windows sur le disque dur et de l'installer automatiquement sans aucune action utilisateur. C'était utile aux non initiés


Haut
Profil Citer
Big Monstro
Sujet du message : Re: [Propose] CD de restauration - Gateway Solo 2150/2550/9300
Publié : 22 mars 2017 22:34
Administrateur
Avatar de l’utilisateur
En ligne
 
Messages : 2897
Inscription : 27 juin 2003 15:15
PC Rétro : 80486 DX2/66, MS-DOS & Windows 95
 
Ces disques n'incluent que des fichiers d'installation, des pilotes et des fonds d'écran ?

J'hésite à accepter, dans la mesure où des ressources pour Windows 2000 sont inclus (donc certainement postérieures au 31 décembre 1999).

Cependant, la date de sortie ne s'appliquent pas aux produits gratuits (on paie pour acheter le matériel, pas les pilotes), je préfère ne pas me prononcer.


Haut
Profil Citer
KeetKhat
Sujet du message : Re: [Propose] CD de restauration - Gateway Solo 2150/2550/9300
Publié : 23 mars 2017 06:04
Membre inscrit
Avatar de l’utilisateur
Hors-ligne
 
Messages : 1737
Inscription : 27 mai 2009 14:04
PC Rétro : IBM ThinkPad 380ED, Windows 95
 
Le premier disque ne contient qu'une interface démarrable et des pilotes, le deuxième disque après analyse j'en ai aucune idée de pourquoi il était fourni avec le PC car il date de 1996 mais il contient des fonds d'écran et des pilotes de cartes assez connu


Haut
Profil Citer
Big Monstro
Sujet du message : Re: [Propose] CD de restauration - Gateway Solo 2150/2550/9300
Publié : 23 mars 2017 13:30
Administrateur
Avatar de l’utilisateur
En ligne
 
Messages : 2897
Inscription : 27 juin 2003 15:15
PC Rétro : 80486 DX2/66, MS-DOS & Windows 95
 
Bon, tu peux nous fournir tes liens ici, a priori c'est bon...

Cela nous permettra de vérifier minutieusement le contenu, et de donner le verdict final.


Haut
Profil Citer
KeetKhat
Sujet du message : Re: [Propose] CD de restauration - Gateway Solo 2150/2550/9300
Publié : 23 mars 2017 19:47
Membre inscrit
Avatar de l’utilisateur
Hors-ligne
 
Messages : 1737
Inscription : 27 mai 2009 14:04
PC Rétro : IBM ThinkPad 380ED, Windows 95
 
C'est fait


Haut
Profil Citer
Big Monstro
Sujet du message : Re: CD de restauration - Gateway Solo 2150/2550/9300 [fr]
Publié : 24 mars 2017 13:44
Administrateur
Avatar de l’utilisateur
En ligne
 
Messages : 2897
Inscription : 27 juin 2003 15:15
PC Rétro : 80486 DX2/66, MS-DOS & Windows 95
 
Après analyse du contenu, il apparait que ces CDs ne soient pas adressés exclusivement aux francophones (beaucoup de texte dans d'autres langues).

Le deuxième disque (de pilotes) reprend un fichier CONTENT.TXT à sa racine. Par souci d'indexation, je reprend son contenu ci-après :
			content of system CD 2.1
Part#		Description			Version		Location			Care of:



		MS Internet explorer (dutch)	3.01		\Misc\intrdypc\MSiexpl\Dutch
		MS Internet explorer (French)	3.01		\Misc\intrdypc\MSiexpl\French
		MS Internet explorer (German)	3.01		\Misc\intrdypc\MSiexpl\German
		MS Internet explorer (Swedish)	3.01		\Misc\intrdypc\MSiexpl\Swedish
		MS Internet explorer (UK)	3.01		\Misc\intrdypc\MSiexpl\English

		Compuserve (Dutch)		2		\Misc\intrdypc\Cserve\Dutch	
		Compuserve (French)		2		\Misc\intrdypc\Cserve\French
		Compuserve (German)		2		\Misc\intrdypc\Cserve\German
		Compuserve (UK)			2		\Misc\intrdypc\Cserve\English


		Western Digital Fast disk drivers		\Win311\Utility\Wd	
		.bmp files					\Misc\Gallery	
		Technical tips (UK) only			\Misc\Techtips
		Video for Windows Runtime			\Win311\Vfwrun	

KBDDSX001ABUS	AnyKey+driverdisk		3.4		\Win311\keyboard	
SWRDSX023AAWW	MS Intellipoint drivers		1.1		\Win311\Mouse\Disk1 & ...\Mouse\Disk2	
7501314		MS intellipoint	for win95	2.0		\win95\mouse
7501598		Win95 promise drivers		1.21		\win95\Promise
7501599		WinNT promise drivers		1.21		\winnt40\Promise
7501569		Int. Controller UATA(PIIX4)			\Win95\pIIx4
SNDDSX006AAFR	Vibra PNP drivers (FR)		1		\Win311\Audio\Vibrapnp\french
SNDDSX006AAGM	Vibra PNP drivers (GM)		1		\Win311\Audio\Vibrapnp\German
SNDDSX006AAUK	Vibra PNP drivers (UK)		1		\Win311\Audio\Vibrapnp\English
SNDDSX021AAWW	Creative Software (FR)		4.28		\Win311\Audio\MMVib16\french
		Creative Software (GM)		4.28		\Win311\Audio\MMVib16\German
		Creative Software (UK)		4.28		\Win311\Audio\MMVib16\English
7501467		Creative Software (FR)		4.33.15		\Win95\Audio\MMVib16\french
7501467		Creative Software (GM)		4.33.15		\Win95\Audio\MMVib16\German
7501423		Creative Software (UK)		4.33.15		\Win95\Audio\MMVib16\English
		Creative Software (FR)		4.28		\Winnt351\Audio\MMVib16\french
		Creative Software (GM)		4.28		\Winnt351\Audio\MMVib16e\German
		Creative Software (UK)		4.28		\Winnt351\Audio\MMVib16\English
VIDDSX032ACEU   Matrox sgram drivers         	1.31.006	\Win311\Display\Mystic
7501388						3.17.047-C	\Win95\Display\SGRAM\French
						3.17.047-C	\Win95\Display\SGRAM\German
						3.17.048-C	\Win95\Display\SGRAM\Dutch
						3.17.047-C	\WIN95\DISPLAY\SGRAM\English
						3.17.048-C	\WIN95\DISPLAY\SGRAM\Swedish
						2.22.064	\Winnt351\Display\SGRAM
						2.30.007	\Winnt40\Display\SGRAM
						1.10.032	\misc\autocad\display\SGRAM
7501541		ATI Rage II+ drivers (Dutch)	3.13 C8Q/S	\Win311\Display\Atirage2\Dutch
		ATI Rage II+ drivers (French)	3.13 C8Q/S	\Win311\Display\Atirage2\French
		ATI Rage II+ drivers (German)	3.13 C8Q/S	\Win311\Display\Atirage2\German
		ATI Rage II+ drivers (Swedish)	3.13 C8Q/S	\Win311\Display\Atirage2\Swedish
		ATI Rage II+ drivers (UK)	3.13 C8Q/S	\Win311\Display\Atirage2\English
		ATI Rage II+ drivers 		3.13 32/29	\Win95\Display\Atirage2
		ATI Rage II+ drivers 		4.00		\Winnt351\Display\Atirage2
		ATI Rage II+ drivers 		4.00		\Winnt40\Display\Atirage2
		

7501435		Plextor	Utility					\Misc\Cdrom\Plextor
NETDSX009ACUS	3COM PCI Busmastering/10-100Mb	4.1		\Misc\Netcrd\3compci			Use setup.bat to install from CD
7501343		3COM ISA			5.0		\Misc\Netcrd\3comisa			Use setup.bat to install from CD
NETDSX004ABUS	3COM XL PCI Adapter		1.2		\Misc\Netcrd\3comXL			Use setup.bat to install from CD
7500633		Olicom Token Ring 		OC-3869D28.0	\Misc\Netcrd\OlicomTR
VIDDSX024ABWW	STB Nitro 5446 drivers		1.1		\Win311\Display\Stb5446 & subdirectories for Autocad.         
VIDDSX024ABWW					1.24B		\Win95\Display\Stb5446    
								\Winnt351\display\stb5446		"to install from NT, the  content of the directory needs to be copied on FD no label"
7501390		STB GX				1.50E		\Win95\display\VirgeGX
						1.0		\Winnt40\display\VirgeVX
						2.2		\Misc\Autocad\display\VirgeVX
7501355		STB Virge/VX			1.24B		\Win95\display\VirgeVX
						1.1		\Winnt351\display\VirgeVX
						1.1		\Winnt40\display\VirgeVX
								\Misc\Autocad\display\VirgeVX

SWRDSX020ABWW	ICU				1.23		\ICU                                                                
								\Disk.ID(Hidden file)		Take care of the Hidden file at the root!
SNDDSX019ABWW   VIVO90 for NT			3.00.10		\Winnt351\Audio\Vivo90
7501210		VIVO90 for NT 4			3.00.11		\Winnt40\Audio\Vivo90
7501217		VIVO90 for WfW311		1.00.07		\Win311\Audio\Vivo90
SNDDSX020AAWW	VIVO90 OS2			5.00.3		\Misc\Os2\Audio\Vivo90

SNDDSX016AAWW	Install Wizard for W95				\Win95\Audio\Ensoniq
SNDDSX023AAWW	Install Wizard for W311				\Win311\Audio\Ensoniq
		Ensoniq PCI,R1			4.02.1028	\Win95\Audio\EnsonPCI\Dutch
								\Win95\Audio\EnsonPCI\French
								\Win95\Audio\EnsonPCI\German
								\Win95\Audio\EnsonPCI\English
						4.00.12		\winnt40\audio\EnsonPCI
						3.30.04		\win311\audio\EnsonPCI
SNDDSX008ACWW	Ensoniq Soundscape		2.00.24B	\Win311\Audio\sndscape
SNDDSX010AAWW	Vibra pnp for NT 3.51				\Winnt351\Audio\Vibrapnp
SWRAPC114AAUS	Voyetra Audiostation2		2		\Win95\Audio\Audista2\Dutch
								\Win95\Audio\Audista2\French
								\Win95\Audio\Audista2\German
7501591						2.00.43		\Win95\Audio\Audista2\English


Par ailleurs, en consultant ce même disque (répertoire ICU), je crois avoir trouvé quelque chose d'intéressant ou d'insolite :
*******************************************************************
*README.TXT                   Release Notes for Plug and Play Kit *
*                                                   for MS-DOS(R) *
*Release 1.23                                       October  1994 * 
*******************************************************************


Introduction
============

This kit contains Release 1.23 of the Plug and Play Kit for
MS-DOS.  The components of this kit are:

Plug and Play Configuration Manager (CM) for MS-DOS.
      Provides configuration services to real-mode and protected-
      mode drivers and to applications in the MS-DOS and Windows
      environments.

Plug and Play ISA Configuration Utility (ICU) for MS-DOS.
      Provides a way to assign system resources to add-in cards
      before the card is installed.  This assignment avoids 
      resource conflicts and keeps track of system resources so 
      that Plug and Play cards do not conflict with non-Plug
      and Play cards in a system.  A full description of ICU 
      features and use is available in the ISA Configuration
      Utility (ICU) User's Guide.



Installation Notes
==================

1) On systems with MS-DOS version 6.0 or later that use a multipath 
   config.sys file, the MS-DOS installation procedure might corrupt 
   the config.sys file by duplicating sections of the file and 
   corrupting the duplicate sections.  If you have this type of 
   config.sys file, verify the integrity of the config.sys file 
   before rebooting your system.  If you see this problem, perform
   the following steps:

   a) Replace the config.sys file with the backup file made by the 
      installation, config.bak.  

   b) Edit the config.sys file and add a line to load the CM driver to
      the beginning of the file.  Here is an example line that assumes 
      the default installation:

      DEVICE=C:\PLUPGPLAY\DRIVERS\DOS\DWCFGMG.SYS

2) The installation procedures in this kit assume that C: is 
   the boot drive of the system.  Therefore, the procedures
   create, make changes to, or overwrite boot drive files on C:.
   In particular, the procedures put the escd.rf file into C:\,
   and create or modify the config.sys file in C:\.  

   On systems without the Plug and Play BIOS, if the boot drive 
   is not C:, but some other drive, the user must move the 
   escd.rf file to the root directory of the boot drive. 
   Also, the user must add line that loads the CM driver 
   (dwcfgmg.sys) to the config.sys file in the root directory
   of the boot drive. 

   Some utilities, for example, the Stacker disk compression 
   utility, can change the boot drive from C: to another drive.
   Such drive changes are not always obvious to the user. In 
   order to avoid the user having to move and edit files, the 
   installation procedure must make an INT 21 call to detect 
   the boot device before installing the escd.rf file or 
   changing the config.sys file.

3) If you have already installed one version (MS-DOS or Windows) 
   of the kit, install the other version in the same directory as 
   you installed the first version.  By default, both versions of 
   the installation use the same directory: c:\plugplay.  

   If you use a different directory, the system configuration 
   information displayed when you invoke the Windows ICU might
   look different than that displayed when you invoke the 
   MS-DOS ICU.

4) If you have already installed the one version of the kit, when
   the second installation procedure asks if you want to replace an
   existing escd.rf file, answer No. If you answer Yes, you will lose
   any system configuration changes you made with the first installed
   version of the ICU.  

   If you inadvertently answer Yes to this question, you can 
   recover the previous version of the escd.rf file by copying the
   c:\escd.bak file to c:\escd.rf.  This recovery is not necessary 
   if you made no system configuration changes with the MS-DOS 
   ICU.

			  NOTE
       The escd.rf file is not used on systems with the 
       Plug and Play BIOS.


MS-DOS Installations
--------------------

1) To install and run the Plug and Play Kit for MS-DOS, your 
   system must have a minimum of 488 KBytes of free conventional 
   memory. 

2) Run the MS-DOS installations for the kit components (INSTALL.EXE)
   from MS-DOS, not from an MS-DOS window under Windows.

3) The MS-DOS install program on these diskettes is incompatible 
   with the expanded memory manager (emm386).  Before installing
   the Plug and Play kit for MS-DOS, disable your expanded memory
   manager. After you have finished the installation, you can 
   enable the expanded memory manager again.

4) The MS-DOS installation fails during an overinstall of a  
   previous version of the Kit if the user has changed the file 
   permissions of the previously installed version to read-only.

5) During MS-DOS installations, you are offered the opportunity 
   to select from one or more choices. The highlighted choice 
   (that is, the choice selected when you press the Enter key) 
   is lighter than the other choices.  On many, but not all, 
   displays, the highlighted choice flashes.
    


****************************************************************** 
*Plug and Play Kit for MS-DOS                                    *
******************************************************************

The components of the Plug and Play Kit for MS-DOS:

- The Plug and Play Configuration Manager (CM)
- The ISA Configuration Utility (ICU)
- The Configuration Assistance Utility (cassist)


Plug and Play Configuration Manager (CM)
========================================

The Plug and Play Configuration Manager provides all of the 
functionality  defined in the "Plug and Play Device Driver
Specification for Microsoft(R) Windows(TM) and MS-DOS".  

The Configuration Manager also complies with the specifications
and definitions in:

  "Plug and Play ISA Specification", Version 1.0a 
      from Intel Corporation and Microsoft Corporation

  "Plug and Play BIOS Specification", Version 1.0a 
      from Intel Corporation, Compaq Computer Corporation, 
      Phoenix Technologies, Ltd.

  "Plug and Play BIOS Extensions Guide", Version 1.21 
      from Intel Corporation

  "PCI BIOS Specification", Version 2.1, from Intel Corporation

  "Extended System Configuration Data Specification" 
      Version 1.02A, from Intel Corporation, Compaq Computer
      Corporation, and Phoenix Technologies, Ltd.
  
This release of the Configuration Manager supersedes all previous
releases.


ISA Configuration Utility (ICU)
===============================

The ISA Configuration Utility provides a way to assign system 
resources to add-in cards before the card is installed.  This 
assignment avoids resource conflicts and keeps track of system 
resources so that Plug and Play cards do not conflict with 
non-Plug and Play cards in a system.

			  NOTE
     The ISA Configuration Utility is for ISA systems 
     only.  Do not run it on EISA systems.  To configure
     EISA systems, use an EISA Configuration Utility.


Configuration Assistance Utility (cassist)
==========================================

On systems without the Plug and Play BIOS, the Configuration 
Assistance Utility (cassist) determines the resources used 
by system (motherboard) devices.

			  NOTE
       The cassist utility is not needed on systems
       with the Plug and Play BIOS.



New Functionality
*****************
Configuration Manager Functionality
=======================================

 /NODCD Option.
   When the /NODCD option is specified and no DCD (Plug and Play
   ISA or PCI device) is present in the system, the driver 
   deinstalls itself from memory. 

 /STATIC Option.
   When the /STATIC option is specified, the Configuration Manager
   remains resident in memory and is not unloaded when there is
   no runtime function active.

 /NOVCPI Option.
   When the /NOVCPI option is specified, the Configuration Manager
   does not use the Virtual Control Program Interface (VCPI) to 
   switch from virtual 8086 mode to real mode (via protected mode)
   prior to calling ACFG BIOS or Plug and Play BIOS run-time
   functions.

Detection of PCI Devices.
   Any PCI device missing from the ESCD image is added and 
   any PCI device no longer present is removed from the ESCD 
   image.

Configuration of PCI Devices.
   Any non-boot/non-PC Compatible PCI device not configured by the 
   BIOS is configured and activated by CM.


ISA Configuration Utility Functionality
===========================================

- The ICU complies with the following three specifications: 
  - that defined by the Plug and Play ISA Specification V1.0.  
  - that defined by the Plug and Play BIOS Specification V1.0
  - that defined by the Plug and Play BIOS Specification V1.0a
  

			  NOTE
       If you find that you cannot disable any PCI 
       devices, then you have an outdated system BIOS. 
       Contact your system vendor for a new version of
       the BIOS.


 Configuration Assistance Utility Functionality
==================================================

Sound Cards Detected.
   cassist detects Soundblaster Pro and Media
   Vision sound cards.

SCSI Adapters Detected.
   cassist detects Adaptec and DPT SCSI controllers.

Plug and Play Cards.
  cassist can run with Plug and Play cards in the system.



Plug and Play Kit Notes and Limitations
***************************************

Release 1.23 of the Plug and Play Kit for MS-DOS has the following
limitations:

- The ICU does not support more than one PCI bus.

- When the CM or ICU move a PCI card, they allocate memory resources
  according to the run-time memory requirement of the card.  If this
  value is smaller than the PCI card's boot-time memory requirement, 
  the BIOS relocates the PCI card the next time the system is booted.
  Therefore, the system boots in a different configuration than that
  last assigned by the CM and ICU.

- The CM and ICU do not take into account the Shadow attribute of the 
  memory blocks.  So, there may be incompatible ROMs in the same
  shadow region.  A workaround for this is to have all off-board
  ROMS use the same mode - shadowed or not shadowed.  The preferred
  mode is not shadowed, since not all cards support ROM shadowing.

- The CM and ICU do not differentiate between 8-bit and 16-bit devices.
  Thus, both device types can be allocated memory in the same 128K 
  block.  Due to ISA bus addressing, this memory allocation method can 
  cause cards to not work.  To work around this problem, design your 
  devices to require memory in 128K blocks.

Configuration Manager Notes and Limitations
===========================================

- Whenever the Configuration Manager executes a 32-bit I/O read to 
  the Plug and Play BIOS the system may hang and/or reset.
  The problem occurs only on systems with a Plug and Play BIOS, Plug 
  and Play software Release 1.21, and EMM386 versions prior to 4.49.  

  To fix this problem, use version 4.49 or higher releases of the 
  EMM386 memory manager.  End-users with earlier versions of the 
  EMM386 memory manager should contact their OEM or Microsoft for
  information on obtaining an updated EMM386 device driver.

- Using the DOS 6.21 or 6.22 Memmaker program with a Plug and Play 
  system may cause system reboots.  Selecting the Memmaker program's 
  "Aggressive" memory scanning option causes Memmaker to specify 
  HIGHSCAN as an option parameter to EMM386 in the config.sys file.  
  The HIGHSCAN option may cause EMM386 to map memory into the F000:0 BIOS 
  space used by the system BIOS.  In this instance,   EMM386 does not 
  recognize that the BIOS may be using the entire 64 KB range from 
  F000:0 to F000:FFFF.  Typically, the system reboots when the 
  Configuration Manager begins initialization, however the behavior 
  may vary from system to system depending upon the BIOS.

  To work around this problem, do not select the "Aggressive" memory 
  scan option on Memmaker.

- Some Plug and Play platform BIOS memory map ESCD into the E000:0 
  block.  Unfortunately, EMM386  does not recognize the presence of 
  ESCD information in the E000:0 range and maps memory on top of the 
  ESCD area.  This corrupts the ESCD storage area.

  To work around this problem, end-users should contact their system 
  OEMs.  OEMs should determine where their BIOS stores ESCD.  If the 
  BIOS maps ESCD into the E000:0 range then end-users and  OEMS should 
  exclude the E000:0 range on the EMM386 command line. A permanent 
  workaround involves BIOS vendors including a BIOS signature in front
  of the ESCD header when using the E000:0 range.

- In the absence of the Intel Plug and Play BIOS extensions, Plug
  and Play boot devices are not reconfigured by the Configuration
  Manager.

- Software exists that is incompatible with proper Configuration 
  Manager operation.  The interaction between this software and 
  the CM might cause unusual system behavior or system delays 
  when both the CM and the software are running on the system.

  If you suspect such interaction is causing problems on your
  system, try adding the /STATIC and/or the /NOVCPI options to 
  the dwcfgmg.sys driver line in the config.sys file.  Either
  or both options might remedy the problem.

- If you use the /FILE option of the Configuration Manager on a 
  system with the ACFG BIOS, and you don't provide motherboard 
  information for the system in an escd.rf file, the ICU cannot
  run.  This option is normally needed only for testing on 
  EISA systems.

ISA Configuration Utility Notes and Limitations
===============================================

- When you save an image file (Save Image File or Save Image File
  As.. on the Advanced menu), the icu.ndx index file is not 
  updated.  So, if the configuration you saved contained one or 
  more unlisted cards, when you load the image file you saved, 
  the card resources for these unlisted cards are in the loaded
  configuration image. However, cards of this type might be listed 
  as "Unknown Card," instead of by the name you assigned
  when you added it.  You can avoid this behavior by choosing the
  Save item on the File menu before you save the image file.  In 
  addition, if you copy the image file to another system, you 
  must also copy the icu.ndx index file to avoid this behavior.

- Pressing the F1 key invokes the ICU help facility from the
  ISA Configuration Utility window (the main window) only.

- When you are modifying a function of a Plug and Play card in 
  preparation for locking it, you might see a conflict message
  that indicates the card is conflicting with itself.  Try 
  reconfiguring the card functions in a different order.

- If a function has two or more resource types that must be 
  configured together, the ICU might not be able to configure 
  that function, even though there might be a valid configuration
  available.  If you encounter this problem, see the discussion 
  on resolving conflicts in the Troubleshooting section of the 
  ICU User's Guide for ways to successfully configure functions 
  in this category.

- When you pick a resource for a new card that is currently used
  by an existing card, the ICU reconfigures the Plug and Play ISA 
  cards first, then the PCI cards.  However, PCI cards are 
  restricted to specific interrupts.  Sometimes, the configuration 
  fails because the ICU assigns Plug and Play cards to all the 
  valid PCI card interrupts.  Then, The ICU cannot configure the 
  PCI cards.  Use the ICU to reconfigure the Plug and Play cards
  to different interrupts, then try again to configure your new 
  card.

- If a boot function on a Plug and Play card causes a conflict 
  error on a system without the Plug and Play BIOS, one of two
  messages appears after you Modify the card and change the 
  function:  

  This card will be configured when the system is rebooted.  
      This may not be true. If this message appears, there 
      is a configuration that works. However, systems 
      without the Plug and Play BIOS lack the ability to 
      configure boot functions of Plug and Play cards, and 
      cannot find the working configuration for you.  

      Find the working configuration and configure the Plug and 
      Play card using jumpers, switches, or a software 
      configuration utility provided by the card manufacturer.  
      Inspect the resources currently used in the system to 
      determine a working configuration.

  A conflict has been detected with <conflicting_card>.  The 
  conflicting resource is <resource_and_value>.
     This message might be inaccurate. It might not inform 
     you of the conflict keeping the card from being configured.

     Inspect the resources currently used in the system and use
     the conflict resolution techniques described in the Chapter
     5 of the ICU User's Guide to discover and correct the conflict.
     If in the course of resolving a conflict reported by this 
     message you see the message discussed previously, use the 
     techniques described to continue.

- Because of ISA architecture limitations, ISA cards cannot use
  Interrupt 2, but must use Interrupt 9 instead.  The ICU takes
  this limitation into account and only allows users to choose
  Interrupt 9 when Interrupt 2 is listed as a valid resource value
  in a configuration file.  When this substitution occurs, the
  interrupt value is offered as "Interrupt 9(2)."

- When you are configuring an unlisted card, if the card 
  manufacturer's documentation lists Interrupt 2 as a valid
  resource value, you must instead choose Interrupt 9.

- A set of reserved resources is standard on ISA systems.  
  However, the ICU mistakenly allows these resources to be 
  allocated by the user.  Please do not allocate the following 
  resources:
	I/O Ports       279h, A79h

- You can increase the size of the Smartdrv buffer to make the ICU
  faster.

MS-DOS ICU Limitations
----------------------

- The MS-DOS ICU installation might fail if some Terminate and 
  Stay Resident (TSR) programs or drivers are resident in memory. 
  If this happens, remove all TSRs from memory and restart the 
  install process. Some example TSRs and drivers are: Borland 
  Side Kick and network drivers that are not loaded from 
  config.sys.

- You might see this message:
	N100: Not enough memory to run the ICU.
  In a few cases, 488 KBytes of free memory is insufficient.  
  In these cases, ICU operation ceases suddenly and you see an 
  MS-DOS "Out of Memory" error.  In this situation, use the 
  Windows version of the ICU if it is available.  If the Windows
  ICU is not available, use the Save item on the File menu 
  after each card operation to avoid losing too much work.  

- You might see this message:
	N110: Please run the ICU from its directory.
  You must invoke the ICU from the directory that contains the DB 
  directory (default placement C:\PLUGPLAY\ICU).    

- You must execute the MS-DOS ICU from MS-DOS only, not from an
  MS-DOS window.  

- If you rearrange the ICU dialog boxes on the screen, you might
  see spurious lines, characters, or buttons.  Do not click the
  mouse on these spurious entities.  Clicking the mouse here 
  causes the system to hang.

- Double-clicking to select an item in a list is not supported.      

- The scroll box (the square slider inside the scrollbar) 
  occasionally does not work.  Use the arrow keys.

- If you initiate an action such as Add Card when the System
  Resource Usage dialog box is visible, the dialog box might 
  close.


Configuration Assistance Utility Notes and Limitations
======================================================

- cassist operation is incompatible with network operation.  
  Disable network drivers on your system before running 
  cassist.  Enable the network drivers after you have run 
  cassist.

- cassist creates the escd.rf file in the root directory of the
  current drive (that is, the drive on which the cassist utility
  is run).  On systems without the Plug and Play BIOS, if the 
  current drive is not the boot drive, the user must move this
  escd.rf file manually to the root directory of the boot drive.

- cassist does not detect interrupt resources used by ISA video 
  cards.

*******************************************************************
* Trademark and Copyright Citations                               *
*******************************************************************


MS-DOS is a registered trademark, and Windows is a trademark of
Microsoft Corporation.

The program used for MS-DOS installation of components of the
Plug and Play Kit for MS-DOS and Windows, INSTALL, is licensed
software provided by Knowledge Dynamics Corp., P.O. Box 780068,
San Antonio, Texas 78278 (U.S.A.). INSTALL is Copyright (c)
1987-1993 by Knowledge Dynamics Corp., which reserves all copyright
protection worldwide. INSTALL is provided to you for the exclusive
purpose of installing the MS-DOS components of the Plug and Play 
Kit for MS-DOS. In no event will Knowledge Dynamics Corp. provide
any technical support for the Plug and Play Kit for MS-DOS.

Other names and trademarks are the property of their respective
companies.

				<END>

Je pense que cela aurait sa place dans cet autre topic >>> viewtopic.php?t=2963


Haut
Profil Citer
Afficher : Trier par : Ordre :
Répondre   Page 1 sur 1  [ 8 messages ]
Revenir à « Dépannage (Bootdisks) »
Aller :