On Sun, 2011-07-17 at 22:13 -0500, Rugxulo wrote:
Using FreeBSD 8-STABLE, a kernel module is produced which is a driver
for the card.
I may be wrong in some of the following.
When building the kernel module, an executable, b43-fwcutter is used to
extract a binary portion of the driver provided by
> So far the pros... The cons are that I have to connect the output
> of one card to the input of the next or use a switch to select from
> which card I want to go to the amplifier. Another thing is that I
> have way too many volume control / mixer channels now :-D
How so? One card is the previou
Hi,
On 7/17/11, Thomas D. Dean wrote:
>
> On Sun, 2011-07-17 at 19:11 -0700, Thomas D. Dean wrote:
>
>> I want to install WATTCP on my FreeDOS system.
>>
>> I have a Linksys Wireless-G Notebook Adapter Model WPC54G Ver. 3.1
>>
>> I have wat2001b.zip. I think I need a packet driver. Correct?
>>
The first line (starting with "UIDE.SYS") stays there for 19 seconds. Then
the second one (starting with "IDE0 Controller") stays there for 49 seconds.
Then I get that error message. In a real machine, UIDE loads lightning
quick.
Screenshot: http://i.imgur.com/7rI2X.png
Juan
On Sun, 2011-07-17 at 19:11 -0700, Thomas D. Dean wrote:
> I want to install WATTCP on my FreeDOS system.
>
> I have a Linksys Wireless-G Notebook Adapter Model WPC54G Ver. 3.1
>
> I have wat2001b.zip. I think I need a packet driver. Correct?
>
> Where may I find a driver for FreeDOS? Google
tomdean,
Yes, you need a packet driver. However I'm not sure about running a wireless
card under DOS - packet
drivers are typically not capable of configuring wireless security. They
normally operate with a wired ethernet
port. Others will know more about this than I.
Is there a reason you
I want to install WATTCP on my FreeDOS system.
I have a Linksys Wireless-G Notebook Adapter Model WPC54G Ver. 3.1
I have wat2001b.zip. I think I need a packet driver. Correct?
Where may I find a driver for FreeDOS? Google returns too many results
to be meaningful.
tomdean
-
> COM file and reassemble it with NASM, simply use NDISASM to
> disassemble, written by the same people as NASM itself :-)
I always wondered what those other executables in the NASM directory were.
I guess I should have read the docs. :)
Thanks!
Jeffrey
-
Hi Jeffrey,
> The FreeDOS wiki says that NASM is the reference assembler. However,
> when I use FreeDOS DEBUG to disassemble (unassemble?) a com file,
> the syntax for addressing memory is not NASM syntax.
This is intentional - DEBUG uses the same assembly language
syntax as MS DEBUG, so existin
Op 17-7-2011 20:30, Jeffrey schreef:
> The FreeDOS wiki says that NASM is the reference assembler. However,
> when I use FreeDOS DEBUG to disassemble (unassemble?) a com file,
> the syntax for addressing memory is not NASM syntax.
I suppose DEBUG mimicks Microsoft's DEBUG. As there is a Microsoft
Hi,
The FreeDOS wiki says that NASM is the reference assembler. However,
when I use FreeDOS DEBUG to disassemble (unassemble?) a com file,
the syntax for addressing memory is not NASM syntax.
C:\ASM>debug psp.com
-u 100,118
Hi!
>> Does anyone here know about connecting two PCI sound cards in FreeDOS?
I have two sound chips: One on my mainboard (something nForce HDA)
and one PCI ForteMedia FM801 (thanks Martin!). The former has good
quality in Linux but is ignored in DOS, the latter sounds worse in
Linux but works p
Hi Andrew,
> You were absolutely spot on with your assessment of my previous FAT
> configuration, re strange file system corruption. Given the vintage of
> the 430CDS I had originally assumed that FAT16 was the best way to
> proceed, but this time with a little more research I reformatted in
> FA
@Bernd and a quick update to all freedos-users,
You were absolutely spot on with your assessment of my previous FAT
configuration, re strange file system corruption. Given the vintage of
the 430CDS I had originally assumed that FAT16 was the best way to
proceed, but this time with a little more re
14 matches
Mail list logo
