At 128 bytes, that is probably the operating system buffer for the UART. Inside some UART there is a FIFO buffer, usually 8 or 16 bytes. There is a threshold level you can set as to when the UART will interrupt the OS to read the buffer. And there is sometimes a way to set the timeout before the buffer is full. This would be set at the hardware level, which you may not have access to.

If the UART has a FIFO you may need to set the level down to 1 so you get an interrupt for each character received. Otherwise the UART will not interrupt until the FIFO is full or some time has passed.

Do you have Carbonite installed? I have been having a problem since they released the latest version. Everything was fine up to that point.

I did every day this week. But I have been riding to work for a year now. Amazing how much you save on fuel. Plus lost 50 pound along the way.

Try running with less than 4GB of RAM and see if that corrects the problem. I had a problem with the built in network adapter on the ASUS motherboard that would cause Vista to crash with more than 4GB. I ended up having to disable the onboard network adapter and put in a PCI card. Now it works just fine.

Just follow the idea in the WTF post from a while back. #define retrun return #define flase false

I think a ski instructor would be cool. I'm with you on computers and technology. I really enjoy programming, especially embedded systems. But if money were no issue, I would only own a computer to look for my next destination.

We could try ignoring him. After a day it will probably go away. The next best thing is delete the account and don't allow new accounts to be created for 24 hours.

I am not sure about the license, but WinPE might be useful. It is a CD bootable version of XP. I have mostly used it for Windows Embedded work. You can get it from the Windows Embedded CD. I don't know if you will be able to run AntiVirus or other tools. But you could at least get files from the drive.

Just swap a couple of numbers around and you get 17:48:59 03/26.

I've been using this one. http://www.journyx.com/[^] The best part is that it's free for up to 10 users.

There might be a complicated solution, but it also seems like there is one that is quite simple. Actually the simple solution would work for up to 18 eggs... Hint, it involves dividing the eggs into 3 groups to start with.

That actually worked. Thanks. The odd thing is that it seems to connect in less than 30 seconds, which was the old timeout value. I set the timeout to 600 seconds. After the first connection, it connects immediately. I guess I will need to connect to the database while the program is initializing to hide the long connect time from the user.

I'm starting to wonder if the Visual Studio 2005 install is bad. This is really weird. I made the small console app you suggested and ran it on the local machine with the database. Here are the results for the 2003 and 2005 version: C:\>"test sql 2003" ServerVersion: 08.00.0194 State: Open C:\>"test sql 2005" ServerVersion: 08.00.0194 State: Open Then I ran it on a remote machine and got: C:\>"test sql 2003" ServerVersion: 08.00.0194 State: Open C:\>"test sql 2005" Unhandled Exception: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error) at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected) at System.Data.SqlClient.TdsParser.ConsumePreLoginHandshake(Boolean encrypt, Boolean trustServerCert, Boolean& marsCapable) at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owning Object) at System.Data.ProviderBase.DbConn

Nothing changed around the SQL connection code. Really only 2 things change: 1) had some classes that needed to override Dispose(). I guess they added Dispose() to the base class. 2) Had to change from .Handle to using the safe handle stuff. The odd thing is that the connection string works when the application is run on the machine with the database. It just won't connect over the network. And that is using the exact same connection string with the Server name specified. Right now the connection string is hardcoded. Later on it will be stored in the registry.

Not sure where to ask this question, so I will start here since I am using C#. I finally got an upgrade to Visual Studio 2005. I converted one of my projects over and cleaned up a few things that VS2005 was complaining about. However, not I can not connect to the SQL server database. If I compile the application with VS2003, the connection works fine. But on VS2005 the connection times out on open. Is there anything different about the SqlConnection object between VS2003 and VS2005? The connection string is a standard: Server=...;User ID=...;Password=...;Database=... (Of course where the ... is filled in with the appropriate data). It seems to work when the database is on the local computer. I just can't connect to a remote computer... -- modified at 13:56 Friday 27th October, 2006

"The airline said that although passengers would be allowed to carry their Dells either as checked or cabin baggage, they could only use them on battery power or through the aircraft power supply available in some first and business class cabins once they have first removed the batteries from the unit." Wow, I would like to see the laptop run on battery power once the battery has been removed from the unit...

You have to pay close attention to details. It says "to install Visual Studio 2005" you need 192 MB of RAM. It didn't say anything about using it after it's installed.