It came more or less set up with everything I needed on it built in and ready for me to use.  After an hour and a half of software updates (yay for updating Ubuntu 10.04) and another hour of installation, the system was set up and ready for me to use as a media server (the original reason why I got the Guruplug).

The snag was where to put it.  I tried to take the unit apart at the power supply unit (PSU) and use the plastic pieces to cover it, but that didn’t work too well, the pieces of plastic that came with it to cover this piece of hardware was insanely difficult to get on to the point that I thought that if I were to need to remove it, I would not be able to.  Instead, I ended up just mounting the D2Plug on the wall of the shelf where it will live.

Man was that a much needed swap.  The Guruplug was originally placed in my basement due to the fact that the server sounded like a hair dryer that was constantly going.  Now when I walk downstairs, all I hear is silence.

Both of these products have been great thus far, I look forward to their future releases .

Have no fear, the information is here:

Username: ubuntu

Password: marvell

Reference Manual: http://www.globalscaletechnologies.com/download/D2Plug_QSG_20111011.pdf

Now to get the JTag port working as well as my other external keyboard

After googling it for a bit, I found the post that explained exactly what to do. The cached toolbox files were screwed up and needed to be regenerated. I started by right clicking and saying “Reset Toolbox” but no luck.

In the end I had to kill all of the tbd files that were created automatically by Visual Studio (more information).

The paths in that post are for Vista and XP, so I found another one that actually defined where to find them in Windows 7 (Visual Studio Application Data Folder).

Make sure to close Visual Studio before trying this or who knows what will happen …

Hope this helps!

gzip.exe -d -f "foo.csv.gz"

The “foo.csv.gz” file will automatically be deleted by gzip and replace it with “foo.csv”

However, if we are archiving these csv files it will take up a fair bit more space, so we wanted to just store the archived version of the flat file.

Originally I thought that I was going to need to unzip them, then rezip all of the files at the end of the process to get the files ready for archival but this took was just a lot of extra processing.

Finally I came across a way to avoid the deletion of the file If you output the file to standard out you are able to then redirect that output stream into your output file (without affecting the original .gz file).

Verdict:

gzip.exe -d -f -c "foo.csv.gz" > foo.csv

This will take all of the contents from the gz file and push it to STDOUT and then with using the >, we redirect the information written to STDOUT to the CSV file where we need it.

Hope this helps

Information based on post from a member on Stack Overflow: http://stackoverflow.com/questions/7351887/gzip-extracting-without-deleting-zip-file

Data File Preview returns the 58 rows which I expected.
Data Viewer returns 57 rows which was not expected.

I tried to redirect any error rows to a flat file, but no success, there were no rows being emitted to the flat file.

I checked in the warnings and saw the following:
[File Connection [1]] Warning: There is a partial row at the end of the file.

I double and triple checked that it had all of the columns (or commas) available. They were all there (why wouldn’t it be? Excel makes valid CSV files).

When I tried to add an empty row in (a row with 13 commas) it was attaching it to the last column which seemed very odd to me. However when I gave it some text, it would capture it as a new row (which is the removed because of the last row vanishing).

It turns out that the row delimiter was messed up. It said “_x003C_none_x003E_” instead of the normal “<none>”.

After changing it back to “” it worked as expected. Very weird.

Hopefully this will stop you from scratching your head and wondering why a single row is randomly being removed from the dataset without rhyme / reason.

Calling object.Dispose() is just a suggestion to say “whenever you want, we don’t need this in memory anymore”. However, because it doesn’t get rid of it immediately, meaning that it is still being referenced which means that the file won’t be able to be deleted immediately.

In order to get around this, you need to call the garbage collector yourself to force the application to get rid of the object from memory.

The Code:

string dest = @"C:\";
FileInfo imageFile = new FileInfo(file);
Image image = ResizeImage(Image.FromFile(file),size);
 
// Save the file to the file system
SaveAsJpeg(image, dest + imageFile.Name, 100);
 
// We don't need the image in memory any more (suggest it to be deleted)
image.Dispose();
 
// Call the garbage collector
GC.Collect();
GC.WaitForPendingFinalizers();
 
// Delete the old file
imageFile.Delete();

The only saving grace now is Windows Backup. I have set it to run every Sunday night and it basically takes an image of all modifications to my C:\ drive and backs it to my secondary drive. Now when a Windows update chooses to have it’s way with my computer, I am able to pop in the recovery CD and have it restore. Yes, it takes a while to run, but I don’t need to format and re-install everything again (a few days worth of installing different versions of Visual Studio and SQL Server).

So then I tried switching it over to the similar function but under the Directory object (Directory.Exists(archiveFullPath)) and it worked like a charm, returning true for the specific directories which I knew existed.

To make a long story short, if you are trying to do anything with a directory, use the Directory object instead of the File because directories aren’t treated the same as files.

void Main(string[] args)
{
    string path = @"C:\testing\";
    string working = path + @"Working\";
    string archive = path + @"Archive\";
 
    // Outputs: false
    Console.WriteLine(File.Exists(path));
 
    // Outputs: false
    Console.WriteLine(File.Exists(working));
 
    // Outputs: true
    Console.WriteLine(Directory.Exists(path));
 
    // Outputs: true
    Console.WriteLine(Directory.Exists(working));
 
    // Put the thread to sleep temporarily
    Thread.Sleep(100000); 
}

Luckily I found a nice set of 2 queries that help to filter out which are the slow queries. They are as follows:

This first query just provides information about some of the queries which are currently being run on the server along with their specific process ids so that we can dig deeper into them later on.

SELECT  p.spid ,
        RIGHT(CONVERT(VARCHAR, DATEADD(ms,
                                       DATEDIFF(ms, P.last_batch, GETDATE()),
                                       '1900-01-01'), 121), 12) AS 'batch_duration' ,
        P.program_name ,
        P.hostname ,
        P.loginame
FROM    master.dbo.sysprocesses P
WHERE   P.spid > 50
        AND P.STATUS NOT IN ( 'background', 'sleeping' )
        AND P.cmd NOT IN ( 'AWAITING COMMAND', 'MIRROR HANDLER', 'LAZY WRITER',
                           'CHECKPOINT SLEEP', 'RA MANAGER' )
ORDER BY batch_duration DESC

After running the first query, you are able to retrieve the process id and then pass that into the following query to receive the actual body of the query being executed (replacing XXX with the actual process id).

DECLARE @spid INT ,
    @stmt_start INT ,
    @stmt_end INT ,
    @sql_handle BINARY(20)
 
-- Fill this in
SET @spid = XXX
 
SELECT TOP 1
        @sql_handle = sql_handle ,
        @stmt_start = CASE stmt_start
                        WHEN 0 THEN 0
                        ELSE stmt_start / 2
                      END ,
        @stmt_end = CASE stmt_end
                      WHEN -1 THEN -1
                      ELSE stmt_end / 2
                    END
FROM    master.dbo.sysprocesses
WHERE   spid = @spid
ORDER BY ecid
 
SELECT  SUBSTRING(text, COALESCE(NULLIF(@stmt_start, 0), 1),
                  CASE @stmt_end
                    WHEN -1 THEN DATALENGTH(text)
                    ELSE ( @stmt_end - @stmt_start )
                  END)
FROM    ::
        fn_get_sql(@sql_handle)

I hope that this helps you as much as it helped me!

Source: http://stackoverflow.com/questions/941763/list-the-queries-running-on-sql-server

I won’t go into much detail about it, but if you are curious search for the ASP.NET Mono Project for more details.

The major issue that I had when setting it up was getting MonoDevelop to install and run.  The other issue was that the JavaScript postback when I was trying to host an ASP.NET 4.0 MVC project however when I went to a ASP 3.5 project, everything worked perfectly.  I will have to look more into why the ASP.NET 4.0 MVC application wasn’t working, but so far I’m happy with it .