Shamus_McFartfinger

LOL!!!

You're welcome.

Shamus, just to let you know that the two links point to the same jpeg (ip2) It confused me at first as I couldn't see any difference at all between the two images... Aww..... crap. Thanks, Digi. Fixed now.

Sure. http://grc.com (One of the best security sites on the net) These snapshots are from different machines on my small lan. I've blurred my IP so knuckleheads don't blast it but you'll see the difference. http://users.tpg.com.au/adsldxhe/ip.jpg http://users.tpg.com.au/adsldxhe/ip2.jpg EDIT: Left an IP showing. Doh! 2nd edit: Use "Shields Up!" on grc.com to test your PC.

Hmm... the jail photo above seems to be missing from his fansite. I guess he won't be appearing on the 27th & 28th January in Hollywood somewhere. http://www.leifgarrettfans.com/

I should ask Digi. It looks kinda Welsh. (Hi Digi!)

Agreed. BTW, a couple of days ago one machine went from a 20MB/sec to 10MB/sec with no changes to drivers, hardware or anything else and has stayed there. Fooking thing. It's one of those Marvel Yukon type thingies on the m/board. Ever had one only partially die before?

What next? Insurance companies being given access to IP addresses of those searching for information on medical conditions or the RIAA & friends targeting users looking for "warez", keygens" or "p2p" under a thinly veiled piracy crackdown? What a crock. Luckily, there's a solution. http://www.v7soft.net/hide-ip-platinum/

Errr.... no.

Yeah. I'd like it faster though. Did you have any luck increasing the packet size (not packet volume) over your network?

That's why I use a striped raid set.

It is gigabit. There's so much crap plugged into the network that I need it.

Hmm...

and for a 12x burn that's way too long indicating problematic ide drivers? Nope. It's pretty good actually. K:\ drive is a shared RAID drive I dump my ISOs onto for burning. When I get a few on there I burn them using 4 machines at once. So... to get 4x across a network while 3 other machines are also requesting large amounts of data from the same drive is pretty good. I do it this way mainly because each machine has different hardware, device drivers, OS and all that other crap that may be buggy. The more things ImgBurn can be tested on, the more reliable Lightning's program will be.

Hint: There's also SATA drives in the machine this log was taken from.

Yeah. It's a mystery. I 18:51:14 ImgBurn Version 1.1.0.5 Beta started! I 18:51:14 Microsoft Windows 2000 Professional (5.0, Build 2195 : Service Pack 4) I 18:51:14 Initialising SPTI... I 18:51:14 Searching for SCSI / ATAPI devices... I 18:51:14 Found 1 CD-ROM and 1 DVD?RW! I 18:52:04 Operation Started! I 18:52:04 Source File: K:\__iso\FUTURAMA_DISC_3.ISO I 18:52:04 Source File Sectors: 2,169,681 (MODE1/2048) I 18:52:04 Source File Size: 4,443,506,688 bytes I 18:52:04 Source File Implementation Identifier: DVD Shrink I 18:52:04 Destination Device: [3:3:0] PIONEER DVD-RW DVR-109 1.58 (F:) (ATA) I 18:52:04 Destination Media Type: DVD-R (Disc ID: RITEKG05) (Speeds: 4x, 6x, 8x, 12x) I 18:52:04 Destination Media Sectors: 2,298,496 I 18:52:04 Write Mode: DVD I 18:52:04 Write Type: DAO I 18:52:04 Write Speed: MAX I 18:52:04 Link Size: Auto I 18:52:04 Test Mode: No I 18:52:04 BURN-Proof: Enabled I 18:52:04 Filling Buffer... I 18:52:11 Writing LeadIn... I 18:52:32 Writing Image... I 19:05:43 Synchronising Cache... I 19:05:57 Operation Successfully Completed! - Duration: 00:13:52 I 19:05:57 Average Write Rate: 5,492 KB/s (4.0x) - Maximum Write Rate: 15,443 KB/s (11.2x)

Agreed. It's one of the reasons I like linux. If an application craps itself the rest of the OS continues regardless. No Blues Screens Of Death etc. Having said that, I find my linux box unusable today after an upgrade last night which seems to have killed it. I wish I knew more about how it works.

I find it's less painful to swear at it and then reboot instead of trying to figure out how to restart it from what remains of the desktop. Seeing as though damned near everything revolves around explorer.exe, and if Explorer crashes, I wouldn't hold out much hope for recovery. That's what the big button is for.

Whatever it is, I'm officially impressed. It's good to see chip makers leave a personal mark on their work. We should all be so lucky. Good find, Mr Junkie.

This was thought of and discussed long before DVD Decrypter bit the dust. i.e. Having a config file in the program directory that could be changed (or copied for config backup purposes) instead of using reg_keys. After much sulking (quite a bit actually), what eventually convinced us that it was a bad idea and Lightning_UK was right was the fact that people have an irritating habit of playing with (or modifying things) they don't understand - particularly config files. To include a modifiable config file for ImgBurn is just asking for trouble. Personally, if you feel the need to set different write rates with different media (I've never bothered to do it yet and I've burned hundreds of CDs and DVDs), your best option might be to use the command line to set different write speeds depending on your task. eg.. imgburn /mode isowrite /start /src k:\ps2.mds /dest f: /speed 4x /deleteimage yes /close imgburn /mode isowrite /start /src c:\stuff\cd.bin /dest e: /speed 32x imgburn /mode isowrite /start /src l:\dvd.iso /dest f: /speed 12x /deleteimage yes Save them as a .bat file somewhere (after reflecting the correct drive letters), and you're laughing. As I said though, I've never bothered. With up-to-date firmware, a decent drive and quality media you can't go wrong.

Cars you've won in Gran Turismo don't count.

It is using DMA and I even did what the FAQ said, didnt work. Any other suggestions? You've deleted/un-installed the IDE controller?

Well, this program won't help you at all. Assuming you've already tried cleaning with rubbing alcohol (isopropyl alcohol) and a lint-free cloth like cotton, you might want to try toothpaste mixed with water. Don't use the whole tube - just a small amount on your *clean* finger and plenty of water then lightly rub the scratches out if you can. Toothpaste is like sandpaper so be gentle.

Ejecting the disk ensures the drive is refreshed before starting the verify process. It adds 10 seconds to the entire process so it's worth leaving on if you wish to verify the media and the files that were written. EDIT: Not ejecting *may* lead to a corrupt disk and/or files passing the verification process.

Yeah. I looking forward to seeing my XR500 (road/trail bike) again one of these days. Only 30 more years to wait.