1. PCI_ALLc.zip Driver
2. ReadMe.txt File Contents

ReadMe.txt Driver File Contents (PCI_ALLc.zip)

From:	Adrienne Electronics Corporation
	Technical Sales & Support 
	(writer - PCI drivers and sample programs for Windows)
			tel: (702)896-1858
			fax: (702)896-3034
			email: info@adrielec.com

To:	Developers (using new PCI time code boards)

Subject:
	Developer Notes for new PCI time code board products.
	Sample source code and programs for use with the the new
	Windows NT, 2000 & 9x device drivers for AEC PCI-TC boards


If you have any questions, suggestions or comments regarding this  
release of the Windows NT, 2000 and 9x device drivers, sample source code and 
applications let me know. I will be happy to keep you up to date on what is 
going on.

Let me know if you find out anything that you feel needs to be changed 
in the driver or sample source code. The Windows NT, 2000 and 9x driver 
are now integratted into the AEC_nttc.dll (Rev. 'C2') while maintaining 
support for the ISA boards as it was with the prior versions of the DLL.  
If you have any desired functions that you would like to see integrated 
into the DLL, let me know and I will see if I can implement some higher 
level processes into it on revision/update.


	General (NT, 2000 & 9x):
The same header file is used for all programs that communicate directly with 
the time code board(s) and do NOT use the DLL inface. This is now an option if 
you are ONLY going to use the PCI based devices. You will not need to use it if 
you write software that only uses the DLL. 


	For Windows NT:
1) Run "install.bat" in the 'InstalNT' directory.
This should set up the registry AND copy the 'aecpcitc.sys' file to
the ...\system32\drivers\ dirctory.
I have included the source code so you can have at it if you want to
incorporate the install in your software. The only requirement that the
program has (as written) is that the driver (.sys) file be in the same
location as the instdrv.exe program. It is this way in the directories
that I have created.
2) Copy the AEC_NTTC.DLL (C2) file to the ...\windows\system32\ 
Directory. With the file in this location, it can be access from 
anywhere in the machine.

	For Windows 2000:
1) When the board is installed, the "Plug and Play" wizard will
let you know that a new 'multimedia' device has been found. Point
the wizard to the 'Instal2K' directory on the diskette and the 
OS should see the device driver (.sys & .inf) and setup files there 
and handle everything with setup and driver copying.
2) Copy the AEC_NTTC.DLL (C2) file to the ...\windows\system32\ 
Directory. With the file in this location, it can be access from 
anywhere in the machine.

	For Windows 9x:
1)Install the time code board and turn on the PC. The machines "PLUG-n-PLAY" 
system should detect the board and ask where the needed files (driver (.vxd) 
and .inf) are located. These files are located in the 'INSTAL9x' directory on
the diskette. 

**SPECIAL NOTE!!! - Only ONE AEC PCI-TC device can be installed in a (9x)machine 
at this time. The device driver does NOT support more than one present. I have 
spent some time trying to get the driver to support additional units, but I 
decided to get some of the other software done (ie: DLL revised...). If you 
need to use more than one device in your machine at the current time, you must 
install under NT/2000 where many devices are simultaniously supported. Sorry 
(more later).


	NEXT:
Once the driver (and DLL) is installed, reboot the PC and you should be able to 
run the .exe program samples included.


-------------------------------------------------------------------------------
This information (these files) is in addition to the printed documentation that 
you received with the time code board(s). I am including text file and .pdf 
documentation that is in additiona to any paper that ships with each board. It is 
contained in the 'BoardDocs' directory. It has files that explain the interface 
protocol and the address (io space) mapping (for LTC/RDR model). The device drivers 
internally handle the interface protocol for sending commands and reading response 
codes.  You will see better as you investigate the sample source code.

If you are going to use DIRECT to driver programming (not using DLL), you will 
need to be aware that the .value parameter of the structure that is passed to 
the driver is always a ULONG (DWORD) in length. You will need to use 'casts' 
to get the data into desired size.  This is coded as a ULONG value, but it will 
contain a BYTE (UCHAR), WORD (USHORT) or DWORD (ULONG) depending upon the 
ACTION! You may want to change the input/output value by CAST or may want to 
implement this data value as a UNION. The driver will NOT care, just so long as 
the 'data size' that is passed to the driver has a 4 byte length. 

You will probably have some questions, just let me know.

Currently, all of the software here is written in C. I hope to get
some other language samples developed, but I will not have any time
for a while. Therefore, If any of you developers would provide me 
with some other (C++, BASIC...) source code that you develop that I 
could use to  provide additional samples for other developers, I would 
appreciate it. I do NOT expect you to give me anything that you consider
to be proprietary. Also, you may use the Visual Basic examples that can
be found within any of the current ISA board distribution diskettes 
and within the zipped files on our web site at 
http://www.adrielec.com/files.htm  --> pc-...zip, NT-Code diretory, VB.
There are also other sample programs there as well. 

Thanks,
	AEC technical support