Audigy 2 support - update

Audigy 2 support - update

[Stephen Hassard]

I haven't tried my Audigy 2 under Alsa for a while. I decided to pop it in my machine tonight and give it a try. I'm using a build from today's CVS.

The Audigy 2 doesn't seem to be listed on the alsa soundcard matrix. Maybe it'll get updated with my results ..

Anyhow, PCM support seems to work fine, tone controls work too. Mixing different PCM sources seems to work well too (playing mp3 from xmms while playing wolfenstein).

sfxload loads soundfonts into the synth, and plays well.

I've connected my midi keyboard to the keyboard port via an adapter, and I can route my midi keypressed to the Audigy 2 synth using my soundfont.

I haven't tried any digital out, but otherwise I haven't seen any problems.

later,
Steve


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Audigy 2 support - update

[Stephen Hassard]

On Thu, May 22, 2003 at 10:12:40PM -0700, Stephen Hassard wrote:
> I've connected my midi keyboard to the keyboard port via an adapter, and I can route my midi keypressed to the Audigy 2 synth using my soundfont.

oops, that should have read joystick port, not keyboard.

later,
Steve


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Audigy 2 support - update

[Florin Andrei]

On Thu, 2003-05-22 at 22:12, Stephen Hassard wrote:

> I've connected my midi keyboard to the keyboard port via an adapter, and I can route my midi keypressed to the Audigy 2 synth using my soundfont.

So MIDI input seems to work, is that what you're saying?

How about MIDI output?

You're using a plain Audigy2, not Audigy2 Platinum, is that correct?

-- 
Florin Andrei

http://florin.myip.org/



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Audigy 2 support - update

[Måns Rullgård]

Florin Andrei <florin@andrei.myip.org> writes:

> You're using a plain Audigy2, not Audigy2 Platinum, is that correct?

Is there a difference, apart from the bundled software and drivers?

-- 
Måns Rullgård
mru@users.sf.net



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Audigy 2 support - update

[Stephen Hassard]

Yup, MIDI input via the joystick port works. My message may not have 
been too clear; Writing messages when you're half asleep is never a good 
idea.

I'm using a plain Audigy2 (not platinum). I obviously don't have the 
LiveDrive! stuff so I can't test out the other mini-din midi port that 
it provides.

I didn't get a chance to try out midi-out to my keyboard, but I'll do 
that tonight and report back.

later,
Steve

Florin Andrei wrote:
> On Thu, 2003-05-22 at 22:12, Stephen Hassard wrote:
> 
> 
>>I've connected my midi keyboard to the keyboard port via an adapter, and I can route my midi keypressed to the Audigy 2 synth using my soundfont.
> 
> 
> So MIDI input seems to work, is that what you're saying?
> 
> How about MIDI output?
> 
> You're using a plain Audigy2, not Audigy2 Platinum, is that correct?
> 



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Audigy 2 support - update

[Stephen Hassard]

On Fri, May 23, 2003 at 12:30:28AM -0700, Florin Andrei wrote:
> On Thu, 2003-05-22 at 22:12, Stephen Hassard wrote:
> How about MIDI output?

MIDI output seems to work fine too.

later,
Steve


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Audigy 2 support - update

[Florin Andrei]

On Fri, 2003-05-23 at 17:43, Stephen Hassard wrote:
> On Fri, May 23, 2003 at 12:30:28AM -0700, Florin Andrei wrote:
> > On Thu, 2003-05-22 at 22:12, Stephen Hassard wrote:
> > How about MIDI output?
> 
> MIDI output seems to work fine too.

Thank you Stephen!

And thanks to the ALSA developers. Now i'll go ahead and buy an Audigy2.
Yeah, it's going to be a Platinum, yeah, maybe a few gizmos on the front
panel won't work (we'll see), but as long as there is at least one pair
of MIDI in/out that works, i'm happy.

Keep up the good work!

-- 
Florin Andrei

http://florin.myip.org/



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Re: Audigy 2 support - update

[Florin Andrei]

On Fri, 2003-05-23 at 01:33, Måns Rullgård wrote:
> Florin Andrei <florin@andrei.myip.org> writes:
> 
> > You're using a plain Audigy2, not Audigy2 Platinum, is that correct?
> 
> Is there a difference, apart from the bundled software and drivers?

I believe the only difference is that the Platinum comes with that nice
and convenient front panel full of connectors and controls. I believe
you can take that panel and stick it into a plain Audigy2 and this way
transform it into an ad-hoc Platinum.

Someone correct me if i'm wrong.

-- 
Florin Andrei

http://florin.myip.org/



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Audigy 2 support - update

[Florin Andrei]

On Thu, 2003-05-22 at 22:12, Stephen Hassard wrote:
> Anyhow, PCM support seems to work fine, tone controls work too. Mixing different PCM sources seems to work well too (playing mp3 from xmms while playing wolfenstein).
> sfxload loads soundfonts into the synth, and plays well.
> I've connected my midi keyboard to the keyboard port via an adapter, and I can route my midi keypressed to the Audigy 2 synth using my soundfont.
> I haven't tried any digital out, but otherwise I haven't seen any problems.

Stephen, do you mind sharing with us the ALSA-relevant part of your
/etc/modules.conf file, please?

Also, what's the distribution you're using, and what's the exact kernel
version?

Thanks,

-- 
Florin Andrei

http://florin.myip.org/



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Audigy 2 support - update

[James Courtier-Dutton]

Florin Andrei wrote:
> On Fri, 2003-05-23 at 17:43, Stephen Hassard wrote:
> 
>>On Fri, May 23, 2003 at 12:30:28AM -0700, Florin Andrei wrote:
>>
>>>On Thu, 2003-05-22 at 22:12, Stephen Hassard wrote:
>>>How about MIDI output?
>>
>>MIDI output seems to work fine too.
> 
> 
> Thank you Stephen!
> 
> And thanks to the ALSA developers. Now i'll go ahead and buy an Audigy2.
> Yeah, it's going to be a Platinum, yeah, maybe a few gizmos on the front
> panel won't work (we'll see), but as long as there is at least one pair
> of MIDI in/out that works, i'm happy.
> 
> Keep up the good work!
> 
I have heard reports that the SPDIF passthru does not work, so you will 
not be able to use external AC3 and DTS decoders.

Can anyone verify this?

Cheers
James




-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Audigy 2 support - update

[Stephen Hassard]

On Fri, May 23, 2003 at 08:44:43PM -0700, Florin Andrei wrote:
> Stephen, do you mind sharing with us the ALSA-relevant part of your
> /etc/modules.conf file, please?

I'm particularly lazy about using modules.conf, so I generally don't bother using it.

I tend to load everything via /etc/modules (debian module auto-loading) in the order that I want the devices to be.

Here's what my /etc/modules looks like:
>>
snd-emu10k1
snd-emu10k1-synth
snd-emux-synth
snd-mixer-oss
snd-pcm-oss
snd-seq-oss
<<

> Also, what's the distribution you're using, and what's the exact kernel
> version?

I'm using debian unstable with a custom kernel. I'm using kernel 2.4.20 w/ the ck patch over at http://members.optusnet.com.au/ckolivas/kernel/ for reduced latency (it make a big difference to the performance of my box). I compiled everything with gcc-2.95.4.

later,
Steve


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Re: Audigy 2 support - update

[Stephen Hassard]

On Fri, May 23, 2003 at 08:39:17PM -0700, Florin Andrei wrote:
> I believe the only difference is that the Platinum comes with that nice
> and convenient front panel full of connectors and controls. I believe
> you can take that panel and stick it into a plain Audigy2 and this way
> transform it into an ad-hoc Platinum.
> 
> Someone correct me if i'm wrong.

Creative Labs seems to change the pinouts on the cards a little bit. I'm not too sure how much things are different between each generation, but my IO module for my SBLive only routed some things when it was hooked up to my Audigy. If you're keeping the IO module with the same generation card that it came with, it shouldn't have any issues.

On that note, does anyone know if you can purchase a digital IO module for the Audigy2 separate from the Platinum package? I wouldn't mind finding one that sits over a PCI slot in my chassis. I don't like cables that hang out the front of my case.

later,
Steve


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Re: Audigy 2 support - update

[Arcady Genkin]

Stephen Hassard <steve@hassard.net> writes:

> On that note, does anyone know if you can purchase a digital IO
> module for the Audigy2 separate from the Platinum package? I
> wouldn't mind finding one that sits over a PCI slot in my chassis. I
> don't like cables that hang out the front of my case.

Have a look at Audigy2 Platinum EX.  Essentially, it's the same as the
regular platinum (i.e. it comes with an internal PCI card), but
instead of the LiveDrive there is an external module full of I/O
connectors.

I have the Audigy2 Platinum Ex, which I purchased for the same reason
as you.  However, I still could not get Alsa's emu10k1 driver to work
with it (neither the recent CVS version, nor the 0.9.3 series). :(  I
get the following error.  SB's emu10k1 driver works, though.

,----[ modprobe output ]
| ice alsa-driver # modprobe snd-emu10k1
| /lib/modules/2.4.20/kernel/sound/pci/emu10k1/snd-emu10k1.o: \
|   init_module: No such device
| Hint: insmod errors can be caused by incorrect module parameters, \
|   including invalid IO or IRQ parameters.
|       You may find more information in syslog or the output from dmesg
| /lib/modules/2.4.20/kernel/sound/pci/emu10k1/snd-emu10k1.o: insmod \
|   /lib/modules/2.4.20/kernel/sound/pci/emu10k1/snd-emu10k1.o failed
| /lib/modules/2.4.20/kernel/sound/pci/emu10k1/snd-emu10k1.o: insmod \
|   snd-emu10k1 failed
`----

,----[ dmesg output ]
| PCI: Found IRQ 11 for device 02:05.0
| PCI: Sharing IRQ 11 with 00:1f.3
| PCI: Sharing IRQ 11 with 02:01.0
| ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:2089: AC'97 0:0 does not respond - RESET
| EMU10K1/Audigy soundcard not found or device busy
`----
-- 
Arcady Genkin

guilt is the cause of more disauders
than history's most obscene marorders (E.E. Cummings)


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Re: Audigy 2 support - update

[James Courtier-Dutton]

Arcady Genkin wrote:
> Stephen Hassard <steve@hassard.net> writes:
> 
> 
>>On that note, does anyone know if you can purchase a digital IO
>>module for the Audigy2 separate from the Platinum package? I
>>wouldn't mind finding one that sits over a PCI slot in my chassis. I
>>don't like cables that hang out the front of my case.
> 
> 
> Have a look at Audigy2 Platinum EX.  Essentially, it's the same as the
> regular platinum (i.e. it comes with an internal PCI card), but
> instead of the LiveDrive there is an external module full of I/O
> connectors.
> 
> I have the Audigy2 Platinum Ex, which I purchased for the same reason
> as you.  However, I still could not get Alsa's emu10k1 driver to work
> with it (neither the recent CVS version, nor the 0.9.3 series). :(  I
> get the following error.  SB's emu10k1 driver works, though.
> 
> ,----[ modprobe output ]
> | ice alsa-driver # modprobe snd-emu10k1
> | /lib/modules/2.4.20/kernel/sound/pci/emu10k1/snd-emu10k1.o: \
> |   init_module: No such device
> | Hint: insmod errors can be caused by incorrect module parameters, \
> |   including invalid IO or IRQ parameters.
> |       You may find more information in syslog or the output from dmesg
> | /lib/modules/2.4.20/kernel/sound/pci/emu10k1/snd-emu10k1.o: insmod \
> |   /lib/modules/2.4.20/kernel/sound/pci/emu10k1/snd-emu10k1.o failed
> | /lib/modules/2.4.20/kernel/sound/pci/emu10k1/snd-emu10k1.o: insmod \
> |   snd-emu10k1 failed
> `----
> 
> ,----[ dmesg output ]
> | PCI: Found IRQ 11 for device 02:05.0
> | PCI: Sharing IRQ 11 with 00:1f.3
> | PCI: Sharing IRQ 11 with 02:01.0
> | ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:2089: AC'97 0:0 does not respond - RESET
> | EMU10K1/Audigy soundcard not found or device busy
> `----
To fix this try: -
lspci
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge 
(rev 03)
00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:10.0 Multimedia video controller: Internext Compression Inc iTVC15 
MPEG-2 Encoder (rev 01)
00:12.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06)
00:12.1 Input device controller: Creative Labs SB Live! MIDI/Game Port 
(rev 06)
00:14.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] 
(rev 08)
01:00.0 VGA compatible controller: nVidia Corporation NV10 [GeForce 256 
SDR] (rev 10)

Notice that 00:12.0 is my SB Live.
Then do: -
lspci -n
00:00.0 Class 0600: 8086:7190 (rev 03)
00:01.0 Class 0604: 8086:7191 (rev 03)
00:07.0 Class 0601: 8086:7110 (rev 02)
00:07.1 Class 0101: 8086:7111 (rev 01)
00:07.2 Class 0c03: 8086:7112 (rev 01)
00:07.3 Class 0680: 8086:7113 (rev 02)
00:10.0 Class 0400: 4444:0803 (rev 01)
00:12.0 Class 0401: 1102:0002 (rev 06)
00:12.1 Class 0980: 1102:7002 (rev 06)
00:14.0 Class 0200: 8086:1229 (rev 08)
01:00.0 Class 0300: 10de:0100 (rev 10)

Notice that 00:12.0 is Class 0401: 1102:0002 (The numbers will be 
different for the Audigy 2)

Now, edit /alsacvs/alsa-kernel/pci/emu10k1/emu10k1.c line 81 onwards: -
static struct pci_device_id snd_emu10k1_ids[] __devinitdata = {
         { 0x1102, 0x0002, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },    /* 
EMU10K1 */
         { 0x1102, 0x0006, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },    /* Dell 
OEM version (EMU10K1) */
         { 0x1102, 0x0004, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 1 },    /* 
Audigy */
         { 0, }
};


As you can see, 0x1102, 0x0002 is my SB Live.
Add a extra line for your Audigy 2 platinum ex.

and recompile, and see if that helps.

Cheers
James



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Re: Audigy 2 support - update

[Arcady Genkin]

James Courtier-Dutton <James@superbug.demon.co.uk> writes:

> As you can see, 0x1102, 0x0002 is my SB Live.
> Add a extra line for your Audigy 2 platinum ex.
>
> and recompile, and see if that helps.

It seems that there already is a line for my card:

,----[ lspci output ]
| 02:05.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
| 02:05.1 Input device controller: Creative Labs SB Audigy MIDI/Game port (rev 04)
| 02:05.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04)
`----

,----[ lspci -r output ]
| 02:05.0 Class 0401: 1102:0004 (rev 04)
| 02:05.1 Class 0980: 1102:7003 (rev 04)
| 02:05.2 Class 0c00: 1102:4001 (rev 04)
`----

So, according to your instructions, my card should be identified by
"Class 0401: 1102:0004", but there already is a line for that in
alsa-kernel/pci/emu10k1/emu10k1.c:

{ 0x1102, 0x0004, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 1 },    /* Audigy */

Am I missing something?  Thanks a lot for your reply!
-- 
Arcady Genkin

guilt is the cause of more disauders
than history's most obscene marorders (E.E. Cummings)


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Audigy 2 support - update

[Pasi Kärkkäinen]

On Sat, May 24, 2003 at 02:13:01PM +0100, James Courtier-Dutton wrote:
> Florin Andrei wrote:
> >On Fri, 2003-05-23 at 17:43, Stephen Hassard wrote:
> >
> >>On Fri, May 23, 2003 at 12:30:28AM -0700, Florin Andrei wrote:
> >>
> >>>On Thu, 2003-05-22 at 22:12, Stephen Hassard wrote:
> >>>How about MIDI output?
> >>
> >>MIDI output seems to work fine too.
> >
> >
> >Thank you Stephen!
> >
> >And thanks to the ALSA developers. Now i'll go ahead and buy an Audigy2.
> >Yeah, it's going to be a Platinum, yeah, maybe a few gizmos on the front
> >panel won't work (we'll see), but as long as there is at least one pair
> >of MIDI in/out that works, i'm happy.
> >
> >Keep up the good work!
> >
> I have heard reports that the SPDIF passthru does not work, so you will 
> not be able to use external AC3 and DTS decoders.
> 
> Can anyone verify this?
> 

I have audigy, and ac3/dts output is not working.

Alsa says it cannot find some hw device.. sorry I don't have the exact error
message here.

I have gotten the same error at least 6 months now..


-- Pasi Kärkkäinen
       
                                   ^
                                .     .
                                 Linux
                              /    -    \
                             Choice.of.the
                           .Next.Generation.


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

Re: Audigy 2 support - update

[Pasi Kärkkäinen]

On Tue, May 27, 2003 at 10:28:47AM +0300, Pasi Kärkkäinen wrote:
> On Sat, May 24, 2003 at 02:13:01PM +0100, James Courtier-Dutton wrote:
> > Florin Andrei wrote:
> > >On Fri, 2003-05-23 at 17:43, Stephen Hassard wrote:
> > >
> > >>On Fri, May 23, 2003 at 12:30:28AM -0700, Florin Andrei wrote:
> > >>
> > >>>On Thu, 2003-05-22 at 22:12, Stephen Hassard wrote:
> > >>>How about MIDI output?
> > >>
> > >>MIDI output seems to work fine too.
> > >
> > >
> > >Thank you Stephen!
> > >
> > >And thanks to the ALSA developers. Now i'll go ahead and buy an Audigy2.
> > >Yeah, it's going to be a Platinum, yeah, maybe a few gizmos on the front
> > >panel won't work (we'll see), but as long as there is at least one pair
> > >of MIDI in/out that works, i'm happy.
> > >
> > >Keep up the good work!
> > >
> > I have heard reports that the SPDIF passthru does not work, so you will 
> > not be able to use external AC3 and DTS decoders.
> > 
> > Can anyone verify this?
> > 
> 
> I have audigy, and ac3/dts output is not working.
> 
> Alsa says it cannot find some hw device.. sorry I don't have the exact error
> message here.
> 
> I have gotten the same error at least 6 months now..
> 

I finally remembered this..

here comes the error-message from mplayer when trying to play movie with
ac3-sound and use the spdif output:


Forced audio codec: hwac3
Opening audio decoder: [hwac3] AC3/DTS pass-through SP/DIF
No accelerated IMDCT transform found
hwac3: switched to AC3, 448000 bps, 48000 Hz
AUDIO: 48000 Hz, 2 ch, 16 bit (0x400), ratio: 56000->192000 (448.0 kbit)
Selected audio codec: [hwac3] afm:hwac3 (AC3 through SPDIF)

Checking audio filter chain for 48000Hz/2ch/16bit -> 48000Hz/2ch/8bit...
AF_pre: af format: 2 bps, 2 ch, 48000 hz, big endian AC3 
AF_pre: 48000Hz 2ch AC3
alsa-init: testing and bugreports are welcome.
alsa-init: requested format: 48000 Hz, 2 channels, AC3
alsa-init: soundcard set to iec958:AES0=0x2,AES1=0x82,AES2=0x0,AES3=0x2
ALSA lib pcm_hw.c:1055:(snd_pcm_hw_open) open /dev/snd/pcmC0D3p failed: No
such device
alsa-init: playback open error: No such device
Could not open/initialize audio device -> no sound.
Audio: no sound


-- Pasi Kärkkäinen
       
                                   ^
                                .     .
                                 Linux
                              /    -    \
                             Choice.of.the
                           .Next.Generation.


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01