Changeset 510
- Timestamp:
- Jul 11, 2010, 5:36:19 PM (15 years ago)
- Location:
- OCO/trunk/install
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
OCO/trunk/install/CHANGELOG.TXT
r403 r510 2 2 UNIAUD CHANGELOG 3 3 ================ 4 5 ===== 1.9.3 and 1.9.23 : July 10, 2010 ===== 6 7 * Malloc fixes 8 9 * Packages are now labeled with both the uniaud16 and the uniaud32 10 version numbers. The first is the uniaud16 version and the second 11 is the uniaud32 version. 12 13 * Improved buffer management (uniaud16) 14 15 * Bug fixes in pause/resume (uniaud16) 16 17 * Application level buffer underrun detection and recovery (uniaud16) 18 19 * Driver level underrun detection and attempted recovery (uniaud32 20 and uniaud16) 21 22 * Removed all debug output from release versions (uniaud16 and uniaud32) 23 24 * Bug fixes for sound capture. 25 26 * Various trap and hang fixes. 27 28 * All above changes by David Azarewicz 4 29 5 30 … … 8 33 * Improved ACPI support, with better support for high IRQ's, 9 34 [Pavel Schtemenko] 10 35 11 36 * Improved interrupt handling and fixes for stream processing 12 37 [Rich Jerant] 13 38 14 39 * No longer leaves devices in "improper state" (ticket #102) 15 40 [Paul Smedley] 16 41 17 42 * Fixed trap on shutdown with SB Live (ticket #109) 18 43 [Brendan Oakley] 19 44 20 45 * Simplified, self-contained install, and a new uninstaller 21 46 [Lars Erdmann] 22 47 23 48 * Revised, and more correct and thorough "README" documentation. 24 49 [Lewis Rosenthal] … … 26 51 * No longer includes support for HDA. 27 52 Please use Paul's 1.9.x Uniaud32.sys for HDA hardware. 28 53 29 54 ===== 1.1.4RC6: April 6, 2008 ===== 30 55 -
OCO/trunk/install/README.DEBUG
r415 r510 1 Description of This Package 2 --------------------------- 1 3 2 Uniaud Debug Package 1.1.4RC6 4 This package is intended to aid in the debugging of Uniaud. It includes 5 both the release and the debug versions of the Uniaud audio drivers 6 (uniaud16.sys and uniaud32.sys). 3 7 4 This package is intended to aid in the debugging of Uniaud. It includes: 8 The production version in the Release directory is compiled without debug 9 output statements and is intended for production use. 5 10 6 * Uniaud32.sys and uniaud16.sys built with DEBUG enabled, from the same source in the same manner 7 as the release. 8 9 * Accompanying map and sym files for use with a debugger or for referencing symbols from the ALSAHLP$ log.11 The debug version in the Debug directory is compiled with debug output 12 statements enabled, and is intended to be used in situations where there 13 is a problem and additional debug information is requested from a developer. 14 The Debug directory also contains MAP and SYM files for use with a debugger. 10 15 11 16 12 Changes from 1.1.4RC6 17 Installation 18 ------------ 13 19 14 * No changes with respect to debug builds 20 You must already have Uniaud installed to use this package. 15 21 16 * Make clean target works now 22 To install the debug version, simply copy the contents of the Debug directory 23 to the \MMOS2 directory on your boot disk and reboot. 24 For example: "copy Debug\* d:\mmos2". 25 26 To install the production version, simply copy the contents of the Release 27 directory to the \MMOS2 directory on your boot disk and reboot. 28 For example: "copy Release\* d:\mmos2". 29 30 You may wish to backup your existing uniaud16.sys and uniaud32.sys files in 31 the \MMOS2 directory first. 17 32 18 33 19 Note that the Uniaud project consists of several components. Only the Uniaud32.sys driver component is 20 distributed under the terms of the GNU General Public License Version 2. The text of the license is in 21 COPYING. 34 How to use the debug version 35 ---------------------------- 22 36 23 To use the debug versions, make a backup copy of your Release uniaud32.sys and uniaud16.sys and copy one 24 or both of the included debug versions in their place. They output more information to the alsahlp$ log 25 than the Release. To create the log file, open an OS/2 command prompt and enter: 37 To use the debug versions, make a backup copy of your Release uniaud32.sys and 38 uniaud16.sys and copy the debug versions in their place. They debug versions 39 output information to the alsahlp$ log and the release versions do not. 40 41 To gather all the information needed to report a problem, download UniLog.cmd 42 from the netlabs ftp: 43 44 ftp://ftp.netlabs.org/pub/uniaud/UniLog.zip 45 46 To create the log file, simply run UniLog.cmd, type a simple 1 line description 47 of the problem, and include the resulting zip file with your problem report. 48 49 To only see the alsahlp$ information yourself, you can open an OS/2 command 50 prompt and enter: 26 51 27 52 copy alsahlp$ uniaud.log 28 53 29 Compiling Uniaud32 requires OpenWatcom 1.7. Either ilink 5.0 or wlink may be used. To use wlink, set 30 USE_WLINK=1 before building. Note also that you must have the DDK and the OS/2 Developer's Toolkit 31 installed. 54 However this log does not contain enough information to debug a problem, so always 55 use the UniLog.cmd program to produce logs to include with a problem report. 32 56 33 Uniaud32 can be built with or without ACPI. The acpidrv.lib api library is required for ACPI support. 57 The Uniaud project site is http://svn.netlabs.org/uniaud. The user mailing list 58 is uniaud-user@netlabs.org, and the developer's mailing list is uniaud-dev@netlabs.org. 59 To subscribe, append "-subscribe" to the portion of the address before the @. The 60 lists are archived on Gmane.org. 34 61 35 To build, first run Configure.cmd. Then run !m_kee.cmd, !m_w4.cmd, or !m_kee_debug.cmd.36 37 The Uniaud project site is http://svn.netlabs.org/uniaud. The user mailing list is uniaud-user@netlabs.org,38 and the developer's mailing list is uniaud-dev@netlabs.org. To subscribe, append "-subscribe" to the39 portion of the address before the @. The lists are archived on Gmane.org.40 41 See also UniInfo.zip, for easily gathering data about a problem for reporting, available from Netlabs FTP. -
OCO/trunk/install/README.TXT
r409 r510 28 28 with integrated audio, built during or after 2004. 29 29 30 HDA is currently better supported in the experimental builds of uniaud32.sys31 which may be downloaded from Paul Smedley's download page:32 33 http://download.smedley.info34 35 Look for the latest uniaud32-1.9.x build, and see installation notes, below.36 37 30 Uniaud also supports some legacy audio hardware. 38 31 … … 56 49 through the process. 57 50 58 If you are not installing support for an HDA card, then simply reboot at the 59 end of the installation; you are likely done (restarting the desktop will not 60 suffice, as the driver needs to be loaded from CONFIG.SYS). If you are 61 installing HDA support, then one file must be overlaid (see the next section 62 for details). DO NOT REBOOT FOLLOWING THE INITIAL INSTALLATION. 63 64 2.3 Installing HDA Support 65 ---------------------------- 66 67 To provide HDA support, you should download the (experimental) HDA-enabled 68 uniaud32.sys as mentioned above. Unzip the distribution to a safe location, 69 peruse the readme, and copy uniaud32.sys on top of the one previously 70 installed in your \MMOS2 directory. Once this is done, as an added precaution, 71 you may want to disable system sounds (these have been known to cause hangs as 72 the desktop comes up, presumably due to the overlapping of them as one event 73 follows quickly after the other). Shut down and reboot (the driver must be 74 loaded from CONFIG.SYS, so merely restarting the desktop will not produce the 75 desired effect). 51 Then simply reboot at the end of the installation. Restarting the desktop 52 will not suffice, as the driver needs to be loaded from CONFIG.SYS. 76 53 77 54 2.4 Device Driver Load Options … … 128 105 4.1 No Sound 129 106 -------------- 130 107 This is typically caused by one of two different issues. Either the speaker 131 108 output levels are set very low (or muted) or the audio device has not not been 132 109 activated (incorrect identification, incorrect/incompatible IRQ, etc.) … … 191 168 ------------------- 192 169 193 This is a close cousin to the condition described in _4.2 Distorted Sound_, 170 Looping sound is defined as a very small fraction of a second of audio playing 171 over and over very rapidly. If you have more than a fraction of a second of 172 audio repeating, such as a whole system sound repeating, that is not a uniaud 173 driver problem and is not covered here. 174 175 Looping sound is a close cousin to the condition described in _4.2 Distorted Sound_, 194 176 and in fact, is a particular type of distortion. Looping is usually caused by 195 177 a card mis-detection or an IRQ conflict. Review the procedures outlined in … … 271 253 272 254 The best option is to use the corresponding debug package for this version 273 of Uniaud and Uni Info.zip, both of which are available from the Netlabs ftp255 of Uniaud and UniLog.zip, both of which are available from the Netlabs ftp 274 256 site: 275 ftp.netlabs.org/pub/uniaud .257 ftp.netlabs.org/pub/uniaud 276 258 277 259 After replacing uniaud16.sys and uniaud32.sys with their debug counterparts, … … 279 261 system to load the debug builds. 280 262 281 Extract UniInfo.zip to a safe directory, and run uniinfo.cmd from there. This 282 will generate a number of logs and will zip them into a single archive, 283 removing the individual log files it has just created. The archive will be 284 located in the directory from which you run uniinfo.cmd. Attach this archive 285 to your bug report. 263 Extract UniLog.zip to a safe directory, and run UniLog.cmd from there. This 264 will create a log file and will zip it into an archive. The archive will be 265 located in the directory defined by your TMP environment variable. Attach 266 this archive to your bug report. 286 267 287 268 All bug reports should go to Uniaud Trac which may be found on: … … 296 277 troubleshooting steps you have attempted prior to raising the ticket. 297 278 298 Finally, per the above recommendation, attach the unilog .zip archive to the279 Finally, per the above recommendation, attach the unilog zip archive to the 299 280 ticket. 300 281 … … 323 304 324 305 Q. I installed MIDI support, but when I click on a Midi file I hear no music. 325 What is happening ? 306 What is happening ? 326 307 327 308 A. Most audio cards don't support MIDI. So if there is no MIDI playback
Note:
See TracChangeset
for help on using the changeset viewer.