Contents
*nix
Related pages
Burning cd's
mkisofs and cdrecord are your friend. The man pages for these programs are excellent but here's a quick example of a session that I have used:
Build the iso file - this is a cross platform iso with support for both Macs (HFS) and Windows (Joliet):
$ mkisofs -P "PublisherId" \
-p "PreparerId" \
-V "VolumeId" \
-A "ApplicationId" \
-r -v -J -hfs \
-graft-points \
-o /tmp/foo.iso \
/=/source/dir
Look for the cdwriter device (note I have an ATAPI cd writer, much like most folk with a regular pc):
$ cdrecord -scanbus
Cdrecord-Clone 2.01-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla
Note: The author of cdrecord should not be bothered with problems in this version.
scsidev: 'ATA'
devname: 'ATA'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling').
scsibus0:
0,0,0 0) 'PHILIPS ' 'DVD+-RW DVD8701 ' '5D24' Removable CD-ROM
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
Write the cd/dvd:
cdrecord -v -sao dev=ATAPI:0,0,0 /tmp/foo.iso
WindowsXP / WinXP
Base software list for a safe and sane installation
Setting up a windows workstation without immediately being compromised can be a struggle, here's a few tools that help:
In addition the following tools make it possible to use windows without the pain and suffering incurred by using the microsoft tools:
Work-arounds for system lock-downs
http://www.petri.co.il/forgot_administrator_password_alternate_logon_trick.htm - Administrator password reset/recovery
http://www.winguides.com/registry/display.php/1097/ - Wallpaper changing via the registry
/WindowsWallpaper - Other ways to change the wallpaper
Outlook
Outlook is an evil, and mostly an unncecessary one - the exchange server should have an IMAP interface on it so that your favourite mail client (for me: mutt) can be used.
With an appropriate html->ascii renderer (w3m, lynx, htmlview, etc.) mutt will do a far superior job showing html messages as plain text (outlook just seems to strip markup leaving almost unreadable emails whenever structural markup has been used
As soon as you learn to decipher text/calendar attachment you should even be able to read your calendar and respond to meeting requests (or perhaps there's an application out there that does this already.
)
- Outlook has a charming habit of saying "You asked for plain text in every possible configuration location, but the moment someone sends me a HTML email I will switch back to HTML for that email"
To which the user would usually say: ARRRRGGGHHHH
This can be fixed (note earlier comment about awful HTML->plain-text conversion) by setting the HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Options\Mail\ReadAsPlain (DWORD) key to 1 (See http://support.microsoft.com/kb/307594)
- Exchange Servers don't use internet standards for mail headers (yes yes, I can here your gasp of astonishment from here...)
When a mail client like Thunderbird displays dates it will attempt to convert them to the local timezone. If the date information is supplied by exchange (at the time of writing, for a particular exchange server, this means without any GMT offset or timezone information) this conversion can be rather painful (sort by date fails completely because the dates are wrong)
Thunderbird can be told to not convert dates, in the user.js file (http://kb.mozillazine.org/Time_and_time_zone_settings#Displayed_dates_and_times) :
user_pref("mailnews.display.original_date", true);
TCP timeouts
The default limit for TCP retries under windows is very small - the result being that even a momentary loss of network connectivity can cause applications like putty to prematurely lose network connections.
As per the putty FAQ (http://www.chiark.greenend.org.uk/~sgtatham/putty/faq.html#faq-timeout):
A.7.11 PuTTY's network connections time out too quickly when network connectivity is temporarily lost. This is a Windows problem, not a PuTTY problem. The timeout value can't be set on per application or per session basis. To increase the TCP timeout globally, you need to tinker with the Registry. On Windows 95, 98 or ME, the registry key you need to create or change is HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\ MSTCP\MaxDataRetries (it must be of type DWORD in Win95, or String in Win98/ME). (See MS Knowledge Base article 158474 for more information.) On Windows NT, 2000, or XP, the registry key to create or change is HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ Parameters\TcpMaxDataRetransmissions and it must be of type DWORD. (See MS Knowledge Base articles 120642 and 314053 for more information.) Set the key's value to something like 10. This will cause Windows to try harder to keep connections alive instead of abandoning them.
Hardware
Memory (RAM)
Failing RAM is really rather painful and sometimes difficult to detect / diagnose. If a system (particularly a new one) starts to misbehave at high loads a memory test would be a good idea.
Here's a couple of tools which I have found useful for diagnosing system memory:
Memtest86 (http://www.memtest86.com/) - Thorough self-booting memory tester
Memtest86+ (http://www.memtest.org/) - fork of Memtest86
Memtest (http://hcidesign.com/memtest/) - Windows-based runtime test. This tool really needs to be run in Safe Mode otherwise false errors are reported.
Video Card
Becnhmark/Testing tools: