-
Posts
30,514 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by LIGHTNING UK!
-
lol don't worry, I was thinking out loud rather than saying 'this is what you should do'
-
You'd need to perform some tests before you could come to any sort of conclusion here. That would basically involve burning a few discs (of the make/MID in question) at each speed and then scan them all to see which is really the best one. You'd probably want to scan them in a mixture of drives too (i.e. Plextor, BenQ and LiteOn) and then take the average.
-
Not so much 'ImgBurn burns with the nearest supported speed' as the drive does. ImgBurn will always tell the drive to burn at the speed you've selected. It's down to the drive to honor that (or not).
-
bootable disc from downloaded iso file
LIGHTNING UK! replied to posthugger's topic in ImgBurn Support
I believe PS2's won't boot random code (which HDLoader is), that's the whole point behind the swap magic discs. It's certainly not anything ImgBurn can/will do though so your best bet is to search a forum dedicated to consoles and alike. -
Yes you can pass it any of the supported image file types and it'll burn you a disc. I'm not really sure what you mean by 'feed' though... you can't pass it data on the fly, the image (or files) must physically exist.
-
Windows XP (and newer) can burn to CD-RW if the IMAPI service is enabled and your drive is supported. It's not drag and drop though unless the CD-RW is specially formatted for that and you install some special software for it (DirectCD / InCD). I believe DVDRAM discs can be used for true D+D if you format them as if they're a hdd - XP has special support for them. Using IMAPI, all that happens is windows sets aside a folder where anything you D+D into the drive window gets copied to, then when you click 'burn' it actually burns the content of that folder to the disc. Sorry, I thought your 2nd problem was the same as the first! The 'show up' term confused me. You mean the drive won't recognise the disc? Yeah it's probably just too old and doesn't support them at all, or has issues with that brand/make of CD-RW (or rather the dye it uses).
-
I just use 'Standard' and not 'ClearType' for that 'Use the following method to smooth the edges of screen fonts' option in 'Display Properties' -> 'Appearance' -> 'Effects'. I run DVI to my monitor and 1920x1200 so blurring of fonts is really not something I want! I like sharp, sharp, sharp
-
If you get the same error on all of them (we need more logs from the better media), it's probably time to clean the drive or replace it.
-
-
I don't get why it's a problem? If it's blank, what do you expect Windows to do with it? Just because it doesn't give the drive a name that corresponds to the media in it doesn't mean it's broken/a problem. So long as your burning utils know what it is, that's all that matters.
-
God that looks ugly with cleartype enabled! The letters are just a blur!
-
When you first turn on your PC there's a screen that flashes up. It'll either be a pretty picture or it'll tell you useful info about your PC. Normally you press DEL or F2 at this point and it'll take you into the bios configuration screen. Keep an eye out next time you reboot, it might even tell you what to press. You can use the 'Pause / Break' key on your keyboard to pause it so the PC won't continue to boot the OS. Then once you're in the BIOS, look around for boot order/priority settings. To be honest, if you aren't sure about that stuff, you probably shouldn't be messing with it - or with Linux! Some things just aren't meant for people with limited PC knowledge.
-
There's no 100% fix for this. It's the price you pay for going 'external'. Sometimes there's just a problem with the controller/enclosure/drive talking nicely to eachother. Just google "The semaphore timeout period has expired" and you'll see what I mean.
-
You've got an ISO of the OS? If so, just follow the 'how to burn an image file' guide. It really doesn't get any easier than that. EDIT: You posted your log It burnt / verifed fine so if it's not booting either the image is corrupt or your machine isn't set to boot from your cd drive. Go look in the bios and change the boot order accordingly.
-
Incompatibility with Windows NT 4.0 (GDI errors)
LIGHTNING UK! replied to Bosanek's topic in ImgBurn Bugs
I work very hard to keep ImgBurn working on 95, 98, NT4 etc and test each one on those OS's via VMWare myself. I have no problem loading it on my virtual machines and the specific calls you're talking about are nothing to do with my own code so I can't work around them. Try the attached dll, it's the one I found on my own install of NT4 - no idea how it got there though, maybe from IE6? EDIT: Even when I delete that file (and I've searched the entire hdd for others), it still runs fine. Msimg32.zip -
When it's done.
-
Labelflash = Mode Page 0x2D LightScribe = Feature 0xFF33
-
Don't 'check' DMA, follow what it says and uninstall your IDE controller from within device manager. At the moment it's limiting you to 2x burn/read speeds.
-
Whatever you want to use. It doesn't really matter if it's DVD+ or DVD-. Just make sure you get some decent discs - Verbatim or Taiyo Yuden. As the drive you've got only supports burning at 8x, I'd suggest you get 8x media rather than newer 16x stuff that it might not support properly.
-
It's a DVD-ROM drive, it can't write discs.
-
It's probably burning the entire disc (with zeroes or something) at the 'close track' bit - as the track would have been reserved and it'll be wondering why nothing has been burnt to it. Get yourself an external drive.
-
Try switching the 'Write Type' in the settings (on the Write tab) to Incremental. 'Command Sequence Error' is totally bogus IMO. The 'sequence' was ok for the previous 788384 sectors, why's it suddenly wrong now?! lol Silly drive!
-
Ooops, my bad. I didn't notice the N. There's nothing stopping you from doing what the rest of my post said though.
-
All you have to do is burn the ISO file! Load it in write mode and burn it to a CDR(W). Or if you have a floppy drive, put it on a floppy disc.
-
Support probably is worse! It's hard to implement these things when you've nothing (including no documentation) to go on. It's far from perfect but it does work. (It'll no doubt need tweaking though)