Jump to content

deomsh

Member
  • Posts

    459
  • Joined

  • Last visited

  • Days Won

    2
  • Donations

    $0.00 
  • Country

    Netherlands

Everything posted by deomsh

  1. HDA2.DLL is limited to 48000 Hz/ 16 bit, so just within the HD Audio specification. MediaPlayer will use DirectSound by default. Did you install DirectX 9.0c already? Players like Foobar can convert 24/32-bit audio to 16 bit. There are old versions, I'm not sure if KernelEx is needed.
  2. On Win9x System Sounds are 22050 Hz/ Low-bit only: Radio Quality. Maybe the driver has problems switching frequency of your Codec. Are sounds on your CD WAV in CD-quality? Further: on my system Playback of media-files is best with Direct Sound output (software emulation only). I think that's not possible in case of System Sounds. Don't know which Device plays them...
  3. Did you already played with the buffer settings of waveaudio? In my opinion best is 5 seconds with HDA2.DLL (default is 4, range=2-9). Can be changed through Control Panel, or in SYSTEM.INI [mci] waveaudio=mciwave.drv 5
  4. About volume with WAVEOUT.EXE: try VolumeWidget=$10 or VolumeWidget=$11 in HDACFG.INI. Always reboot!
  5. Please run MEM /A/C/P first and upload print-screens/ photo's
  6. Good! There is a program included with volume sliders: WAVEOUT.EXE (copy to %windir% and open with "Run"). The pops are always there, more advanced drivers wait a while before giving signal to the output. Are others system sounds better afterwards? At first run buffers have to be filled up. One possibility is 'editing' your startup sound with one second of silence at the beginning of the file (difficult, I didn't make it). The HD Audio Controller is part of the chipset, sent/ receives digital HD Audio to/ from the codec. Sigmatel 9205 is your codec, doing digital/ analog conversion and much more. HDATSR has a buffer in memory, no longer available to Windows. This means jack-sensing is'nt activated in the right way in the codec. Some laptops have switches in the jack, yours probably not. If you like I can take a look in the codec-datasheet and other sources. Maybe some extra Verbs can be written to HDAICOUT.HDA
  7. Probably start here: https://en.m.wikibooks.org/wiki/First_steps_towards_system_programming_under_MS-DOS_7/The_PC_keyboard
  8. You can try various Windows 98SE shutdown fixes. They are on http://www.mdgx.com/web.htm Read carefully first! BTW I was mostly unsuccesfull with those fixes if I had shutdow issues.
  9. About the shutdown issue, try: 1) Reinstalling video drivers (if already installed). 2) Is there different behavior with/without ACPI (see pages 8-10 of the D600-thread). Question: is Reboot to MS-DOS okay?
  10. Are you sure your D830 has no problems? I have been reading some posts about connectivity problems with D830. Of course not involving Windows 98SE, you're the only one who is trying. Was your D830 connecting 'under' another OS? I have no ideas, otherwise than trying other cables (was an issues with my wife's HP laptop). Or disabling modem/wireless, so playing with BIOS-settings. I have no access to a D830 as you know. Addressing shutdown problems only after your ethernet is actually connecting.
  11. You can make menuitems. This post gives an idea: https://retrocomputing.stackexchange.com/questions/6801/how-do-i-create-a-boot-menu-to-select-between-windows-and-dos
  12. About your 'problems': USB MS-DOS drivers are designed in this way. I am not aware of any 'hot-pluggable' versions. So there is no 'fix', there is no 'problem'.
  13. Did you try already Win98 driver from this package: 9720PVista32-64Lan.zip ? Contains WIN98SE and WINME drivers too.
  14. Are you sure there are no BIOS-related settings involved? https://www.dell.com/community/Networking-Internet-Bluetooth/Dell-Latitude-D830-cannot-connect-to-internet/td-p/5132953
  15. About ethernet: I have no experience with Broadcom. But I found this site, maybe there's something 'in it' for you, although it's about Win9x on a D600: https://www.vogons.org/viewtopic.php?f=61&t=47505
  16. https://en.m.wikibooks.org/wiki/First_steps_towards_system_programming_under_MS-DOS_7/Selected_drivers
  17. MS-DOS doesn't need drivers for internal Floppy disks nor Hard disks, if the Hard disks are set in BIOS to IDE-mode (if they are SATA). Your CD-drivers seems to be NOT correct in your CONFIG.SYS / AUTOEXEC.BAT. Both CDROM.SYS and MSCDEX.EXE should have the SAME entry, like /D:MSCD000
  18. You can begin with DIR A:\ /p to see if the drive exists and to view the content of the root directory of drive A: - and so on for all available drives. If you want to give some command on a certain drive (run a program or whatsoever), just type the 'drive-letter' and ':' and give 'Enter' - according to the example above: A: and you are 'on' that drive. If you want to 'call' a program while 'on' another drive, include the drive. Example: D:\SOMEPATH\APROGRAM.EXE
  19. Don't know. You can REM lines one at a time to search if there is an entry causing this behaviour. Maybe start with the ANSI.SYS-line. Type 'REM ' at the beginning (without quotes) and reboot. BTW Why are you using COMMAND.COM from C:\WINDOWS\COMMAND instead from C:\WINDOWS ?
  20. Normally HIMEM.SYS and EMM386.EXE are in the Windows-directory, NOT in WINDOWS\COMMAND. I'm not sure about ANSI.SYS - search with DIR ANSI.SYS /s from the command-line (can take a while).
  21. This is '98 SE MDCU' version 3.05. More info: http://www.msfn.org/board/index.php?showtopic=89232 I am not allowed to give a download link, it's on mdgx' site. Name of the file will be MDCU.ZIP. If you found any infected files you have to report to mdgx.
  22. The article gives a link to the DOS date/time format. But following this link gave me a 403 Forbidden Error. Luckily the link is stored in the Wayback-machine. First 2004-entry gives information below (and a nice picture, not nice anymore in the quote): "Number four: The DOS date/time format The DOS date/time format is a bitmask: 24 16 8 0 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ |Y|Y|Y|Y|Y|Y|Y|M| |M|M|M|D|D|D|D|D| |h|h|h|h|h|m|m|m| |m|m|m|s|s|s|s|s| +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ \___________/\________/\_________/ \________/\____________/\_________/ year month day hour minute second The year is stored as an offset from 1980. Seconds are stored in two-second increments. (So if the "second" value is 15, it actually represents 30 seconds.) These values are recorded in local time. November 26, 2002 at 7:25p PST = 0x2D7A9B20. To convert these values to something readable, convert it to a FILETIME via DosDateTimeToFileTime, then convert the FILETIME to something readable." https://web.archive.org/web/20040614163825/http://blogs.msdn.com/oldnewthing/archive/2003/09/05/54806.aspx EDIT: this looks like the 'math' needed (hex-binary-decimal, done with a converter-website). Please correct me if I'm wrong. MS-DOS DATE/TIME FORMAT LITTLE ENDIAN: 20 9B 7A 2D HEX: 0x2D7A9B20 BIN: [0010110] [1011] [11010] [10011] [011001] [00000] DOS: [yyyyyyy] [mmmm] [ddddd] [hhhhh] [mmmmmm] [sssss] DEC: [22] [11] [26] [19] [25] [0] DATE+TIME: 2002 / 11 / 26 / 7:25:00 pm BTW I added the Little Endian bytes. Excercise in behalf of Wunderbar, no calculator needed: Little Endian: 01 a9 82 4e Hexa-decimal: 0x4E82A901 Decimal => Binairy 4 0100 E=14 1110 8 1000 2 0010 A=10 1010 9 1001 0 0000 1 0001 yyyyyy 0100111 = 39 mmmm 0100 = 04 ddddd 00010 = 02 hhhhh 10101 = 21 mmmmmm 001000 = 08 sssss 00001 = 01 = x2 1980+39 => 2019/04/02 9:08:02 pm
  23. I never experienced any problems with http://www.mdgx.com/web.htm
  24. You're going a bit too fast for me. 1) If SESP21A gave problems, try another one, like 98 SE MDCU. Best is after reboot going in Safe mode first to fully finish the installation. 2) Did you combine a Stage One installation with the unofficial Intel inf-updates from @LoneCrusader ? And of course with driver updates like MDCU. About DosLFN-drivers: I have no real experience, but you can find much on mdgx' site.
  25. Thanks, I see no errors in the procedure. You can continue in three different directions. 1) Updating Drivers. Did you already tried the Unofficial Service Pack I suggested earlier? 2) Take your loss and try using your MS-DOS CD-ROM-drivers inside Windows (some drawbacks: at least no Long File Names, burning software will not work and no digital audio available). Just un-rem MSCDEX in AUTOEXEC.BAT. 3) Trying a new installation in a Windows-directory with a different name, with following procedure in two stages. Stage One: installation without PCI-BUS to determine if CD-ROM acces is possible at all. If not, you're lost in space. If there IS actually CD-ROM access, continue with Stage Two. Stage Two: first delete Standard VGA (without reboot!) and then manually add the PCI-BUS with Add New Hardware Wizard and continue installing PCI-Devices. Following setup-line is needed for Stage One: SETUP /P I,S=DETECTBUS,DETECTFLOPPY (watch the space between P and I). Instead of 'I' an ACPI installation is possible too, with 'J' instead of 'I'. Depends on the 'desired' installation in Stage Two. BTW skipping detection of the Floppy Disk Controller by adding DETECTFLOPPY is not stricty necessary, but can be helpfull *somehow*.


×
×
  • Create New...