Install SCO Openserver 5.0.7 as a trial


 
Thread Tools Search this Thread
Operating Systems SCO Install SCO Openserver 5.0.7 as a trial
# 1  
Old 08-05-2010
Install SCO Openserver 5.0.7 as a trial

hi

Howto install SCO Openserver 5.0.7 as a trial or howto get a trial license number?
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. SCO

install iperf on SCO OpenServer 5.0.7

hi Howto install iperf on SCO OpenServer 5.0.7? (0 Replies)
Discussion started by: ccc
0 Replies

2. SCO

Need help to install sco openserver 5

Hi, Im installing sco openserver 5 (OpenServer-5.0.7Hw-10Jun05_1800.iso) on a vmware server 1.0.4. Installation is ok but on when x server is loading i just can login, mouse does not move and most of keyboard cases do not respond. I choose usb mouse + french keyboard while installating, should i... (1 Reply)
Discussion started by: sup69
1 Replies

3. SCO

Install NIC on SCO openserver 5.0.2

Hi I am trying to install NIC FastNic 10/100 PCI Ethernet driver into PCI# 3 of the GA-SIML Rev 1.0 Motherboard on 1GB Hard-disk driveI have following the instruction on the CD-Disk and when I added NIC by netconfig and I do not know what is the following question: PCI BUS# DEVICE#... (3 Replies)
Discussion started by: TinhNhi
3 Replies

4. SCO

Install SCO Openserver 6.0.0 on an IBM x3500 7977E6U

Even though IBM states that the x3500 server is Openserver 6.x compatible, it is still a bit of a trick to install SCO Openserver 6 to the machine because the standard method of installing the BTLD required to install the OS requires that the driver be written to a floppy which doesn't exist on... (3 Replies)
Discussion started by: qkrenge
3 Replies

5. UNIX for Dummies Questions & Answers

How to install and configure Apache on SCO openserver 5

I have just been made responsible for setting up Apache on our office SCO box. I have searched the internet, but haven't found any details that I can make sense of. I'm unfamiliar with Unix and would appreciate any help members of the forum have to offer. (1 Reply)
Discussion started by: cstovall
1 Replies

6. Filesystems, Disks and Memory

SCO openserver 5 install problem

Hello all, I'm trying to install SCO openserver 5 on a 2.5 Gig hard drive, and I tried fdisk and a low-level format of the drive. When I insert the boot diskette all seems fine, and it asks me to set the cd-rom and it sees it and reads from it. Well, I'm thinking all is well until right after I... (1 Reply)
Discussion started by: immulett
1 Replies
Login or Register to Ask a Question
TRIAL(1)																  TRIAL(1)

NAME
trial - run unit tests SYNOPSIS
trial [options] [[file|package|module|TestCase|testmethod]...] trial --help DESCRIPTION
trial loads and executes a suite of unit tests, obtained from modules, packages and files listed on the command line. trial will take either filenames or fully qualified Python names as arguments. Thus 'trial myproject/foo.py', 'trial myproject.foo' and 'trial myproject.foo.SomeTestCase.test_method' are all valid ways to invoke trial. -b, --debug Run the tests in the Python debugger. Also does post-mortem debugging on exceptions. Will load '.pdbrc' from current directory if it exists. -B, --debug-stacktraces Report Deferred creation and callback stack traces --coverage Generate coverage information in _trial_temp/coverage/. Requires Python 2.3 or higher. --disablegc Disable the garbage collector. I don't know why this is in trial. -x, --extra Add an extra argument. (This is a hack necessary for interfacing with emacs's `gud'.) -e, --rterrors Print tracebacks to standard output as soon as they occur --force-gc Run gc.collect() before and after each test case. This can be used to isolate errors that occur when objects get collected. This option would be the default, except it makes tests run about ten times slower. -h, --help Print a usage message to standard output, then exit. --help-reporters Print a list of valid reporters to standard output, then exit. --help-reactors List the names of possibly available reactors. -l, --logfile <logfile> Direct the log to a different file. The default file is 'test.log'. <logfile> is relative to _trial_temp. -n, --dry-run Go through all the tests and make them pass without running. -N, --no-recurse By default, trial recurses through packages to find every module inside every subpackage. Unless, that is, you specify this option. --nopm Don't automatically jump into debugger for post-mortem analysis of exceptions. Only usable in conjunction with --debug. --profile Run tests under the Python profiler. -r, --reactor <reactor> Choose which reactor to use. See --help-reactors for a list. --recursionlimit Set Python's recursion limit. See sys.setrecursionlimit() --reporter Select the reporter to use for Trial's output. Use the --help-reporters option to see a list of valid reporters. --spew Print an insanely verbose log of everything that happens. Useful when debugging freezes or locks in complex code. --tbformat <format> Format to display tracebacks with. Acceptable values are 'default', 'brief' and 'verbose'. 'brief' produces tracebacks that play nicely with Emacs' GUD. --temp-directory <directory> WARNING: Do not use this options unless you know what you are doing. By default, trial creates a directory called _trial_temp under the current working directory. When trial runs, it first deletes this directory, then creates it, then changes into the directory to run the tests. The log file and any coverage files are stored here. Use this option if you wish to have trial run in a directory other than _trial_temp. Be warned, trial will delete the directory before re-creating it. --testmodule <filename> Ask trial to look into <filename> and run any tests specified using the Emacs-style buffer variable 'test-case-name'. --unclean-warnings As of Twisted 8.0, trial will report an error if the reactor is left unclean at the end of the test. This option is provided to assist in migrating from Twisted 2.5 to Twisted 8.0 and later. Enabling this option will turn the errors into warnings. -u, --until-failure Keep looping the tests until one of them raises an error or a failure. This is particularly useful for reproducing intermittent failures. --version Prints the Twisted version number and exit. --without-module <modulenames> Simulate the lack of the specified comma-separated list of modules. This makes it look like the modules are not present in the sys- tem, causing tests to check the behavior for that configuration. -z, --random [<seed>] Run the tests in random order using the specified seed. AUTHOR
Written by Jonathan M. Lange REPORTING BUGS
To report a bug, visit http://twistedmatrix.com/bugs/ COPYRIGHT
Copyright (C) 2003-2008 Twisted Matrix Laboratories This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU- LAR PURPOSE. Oct 2007 TRIAL(1)