search for: kooky

Have you ever lingering on the classic as well as memorable smile with tears of Princess Anny in ?Roman Holiday?? Have you ever been fascinating about the song of Do, Ra, Mi in ?Sound of Music?? Have you ever been motivated by the determination and absorption of what he is doing of Forest Gann? Have you ever been blown away by resolution to struggling for freedom and shed tears for the beautiful

Hello All, Just a short note to add my vote for a HUGE round of applause to the CentOS team for their untiring efforts in getting releases out the door. I've just upgraded several servers to 5.6 and it all "just works". None of the team's work is easy to accomplish, especially when less-than-useful complaints keep popping up from thoughtless users who don't appreciate

This isn''t Rails or Ruby related, but I just need some advice and thought I''d ask the bright individuals here. I want to start my own blog but I''m not sure where to begin. I don''t want to get a blogger account because I want to have my own domain. Blogger also doesn''t have many features. My hosting service is 1AND1 so it supports php, cgi and mysql.

All, In winxp & 2k for that matter, you have the ability of saving shortcuts to network places in the my network places. When some of my users try to access these shortcuts(to a samba share) in winxp, it takes a horrendous amount of time for the folders to populate the screen. Especially when viewing in windows explorer with the folders view button depressed. Under tools>folder

Ha ha! I'm don't know what change I made that cleared up the errors, but I can figure that out later. Of course, I immediately tested my new oggenc. Using the same input file and default options, I get these results: [MSVC] File length: 4m 21.0s Elapsed time: 0m 54.0s Rate: 4.8333 Average bitrate: 129.6 kb/s File size: 4,229,428 [BCB]

Per a discussion I started earlier, I've encoded a wav with oggenc's from various different compilers. And so... MSVC (as distributed on vorbis.com): 3,502,399 bytes BCC (WinME, BCB4 Std SP 1): 3,502,555 bytes EGCS (Linux 2.4.1, egcs 2.91.66): 3,516,935 bytes GCC (Linux 2.4.1, gcc 2.95.2): 3,516,935 bytes BCC, EGCS, and GCC I compiled myself from last night's CVS snapshot. The

I realize not many people (one :) ) want to build vorbis with BCB, but what about vorbisfile.c, os.h, oggenc.c, and getopt? And someone must care about the MSVC files. I really tried not to bring up any questions about BCB itself (although I had some). Please, someone, take a look at the original message, and excuse me if I'm too impatient...

After downloading the nightly snapshot last night, I've spent a good part of the day trying to build the package with Borland C++Builder 4. I have some things to report, and also need some help. [Note: this message is long and messy :)] {Converting DSP files to BPR files} I made the necessary BPR files from the DSP files with the Visual C++ Project Conversion Utility. This works okay

...le. Minor clean ups. ~ Current native mode setting code. Not yet used by driver. ~ Log video RAM size in decimal rather than hex. D'oh! ~ Fix comment in XG47GetFramebufferSize to reference correct page in docs. ~ Fix command list submission on big-endian. ~ Eliminate kooky color byte-order swapping. ~ Trivial clean-ups in XG47SetCRTCViewStride ~ Rework command list tracking ~ Log error message if too much data is written to command list. ~ ifdef out more code when NATIVE_MODE_SETTING is defined ~ Replace xg47_BeginCmdList with xg47_BeginCmdLi...

...s very strange. Even the old Macintoshes on my LAN outcopy NT (~700KB/sec thru netatalk). I've enclosed some packet sniffer logs, where you can see the vast differences in the way the data is being thrown around the wire. Note, it's strange because it's clear there's something kooky going on with the sequence # and ack# stuff, as well as the payload area itself. On the fast direction (NT->UNIX), the proto analyser gives clean NetBIOS area decodes. But on the SAMBA->NT one, it warns about an invalid type, and a "probably continuation of prior transaction"...

>The Digium cards actually are sharing IRQs with other devices -- the >installer mentioned it could be an issue initially, but when he saw that >the devices that the cards were sharing with were the network card and >the video card, he said to just try and see if it works first. Sounds >like some of the problems that we're having could be related to this, >and it's