Changeset 311 in xtideuniversalbios
- Timestamp:
- Mar 11, 2012, 1:16:56 AM (13 years ago)
- google:author:
- gregli@hotmail.com
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
wiki/SerialDrives.wiki
r310 r311 28 28 29 29 * 2. Open a command prompt, and run the SerDrive utility on the server. * Arguments are described below. In its simplest form: 30 C:/> SerDrive MyImage.img30 {{{ C:/> SerDrive MyImage.img }}} 31 31 If you do not already have an image, you can obtain boot floppies of FreeDOS from. 32 32 SerDrive will use the first available COM port by default, at a speed of 9600 baud (which is reliable, but relatively slow, you will likely want to increase this for continued use). … … 48 48 = SerDrive Command Line Arguments = 49 49 50 * Usage: SerDrive [options] imagefile [[slave-options] slave-imagefile]*50 * {{{ Usage: SerDrive [options] imagefile [[slave-options] slave-imagefile] }}} * 51 51 52 52 * _Specify Disk Geometry:_ -g [cyl:head:sect] * … … 112 112 * COM port on the server machine capable of high speed operation. Most motherboard based COM ports can NOT attain high speed. However, most USB COM ports can attain high speed, check the product documentation if it states "Data Transfer Rate: 500kbps" or similar. USB serial ports that have been tested with the BIOS: 113 113 * [http://www.trendnet.com/products/proddetail.asp?prod=265_TU-S9&cat=32 TRENDNet TU-S9] 114 * [http://www.iogear.com/product/GUC232A/ IOGear GUC232A] 114 * [http://www.iogear.com/product/GUC232A/ IOGear GUC232A], although beware that the specs only list up to 230Kbps, in limited practice it has worked up to 460K. 115 115 116 116 Care must be taken when configuring the serial connection - the clock multiplier is not detectable by the client PC. With a 4x clock multiplier, the client PC should be set to 115.2K baud, while the matching server needs to be set to 460.8K baud.
Note:
See TracChangeset
for help on using the changeset viewer.