Question about UPS Battery Backup Systems
Tells me to install module system32.Is this something i have to buy?
could you please help me?
the valid name of the product is lexmark 4200 series, it is a printer,scanner,fax machine
Most modules are available from CPAN - the Comprehensive
Perl Archive Network. They are supplied in what is known as a tarball. A
tarball is a gzip compressed tar file. When a module is made the directory structure
it lives in is converted to a single file that contains both the files and the
directory information. A program called tar performs this function and the
resultant file is called a tar file. Tar files have a .tar file extension. This
tar file is then compressed using the gzip (GNU Zip) program. Gzipped files have
a .gz extension thus a standard module will be called something like:
Some-Module-0.01.tar.gz The first part is the name, the next part the version number and the last part the .tar.gz extension signifying that this is a tarball. You uncompress a tarball using the tar program like this (the $ represents the command prompt):
$ tar -zxvf Some-Module-0.01.tar.gz All *nix systems will have a tar program. On windows you can use CYGWIN which is a set of UNIX tools ported to Win32 to get tar but programs like WinZip will handle extracting tarballs just fine.
One issue with Winzip is that it does not deal well with .tar.tar as an extension. Fix it by changing the extension to tar.gz. Once your have extracted your tarball you then need to make and install your files. You do that like this. At the command prompt navigate your way to the directory created where you extracted the tarball. Making your extractions in a /temp dir is a good idea in case of problems with badly made distributions. There may be several directories to move through. In our hypothetical example above we would expect the tarball to extract into a directory called "Some-Module-0.01", however it may extract to "Some" or even straight into the current working directory (this is not fun to clean up, thus the suggestion of using a /temp dir). Within this module directory we should find a file called "Makefile.PL" although it *may* be several dirs deep. Once you find the Makefile.PL you do the following:
$ perl Makefile.PL
$ make test
$ make install This should all proceed smoothly and your module should be installed, if not see below. Note on Win32 you will need to use a program called nmake. You can get a copy from M$ here: nmake via FTP or here nmake via HTTP Once you have downloaded it you need to run the program (it self extracts) and make sure that you do this in a directory that is on your PATH. The PATH is a list of directories that Win32 will search for executable files. When you type nmake you want Windows to be able to find the program so it must be in one of the directories on the PATH. To see your current PATH type PATH at the command prompt. C:\WINDOWS or C:\WINNT will be a fairly safe bet.
Now that you have got nmake and extracted it in a directory on your PATH you just do this:
C:\> perl Makefile.PL
C:\> nmake test
C:\> nmake install
Ok either everything went fine or you got some errors. Note in the following read nmake for make if your are on Win32
Posted on Nov 23, 2008
Tips for a great answer:
Jan 16, 2014 | UPS Battery Backup Systems
Dec 08, 2008 | UPS Battery Backup Systems
Jun 10, 2008 | UPS Battery Backup Systems
Dec 29, 2007 | UPS Battery Backup Systems
Dec 17, 2007 | UPS Battery Backup Systems
Nov 23, 2007 | UPS Battery Backup Systems
Nov 07, 2007 | UPS Battery Backup Systems
31 people viewed this question
Usually answered in minutes!