Jump to content

All Activity

This stream auto-updates

  1. Last week
  2. Earlier
  3. If that is pretty much a offline computer then it's not a problem to continue using WinXP. but if you use it online for browsing websites fairly regularly it's unwise to use that as even looking at Firefox and Chrome browsers it appears they dropped support of those on Windows XP years ago as if you can't install a recent version of those there is likely plenty of flaws one could exploit in the browser just by visiting a compromised site. so even if you want to roll-the-dice a bit, even assuming you can find a half way decent updated browser, I would avoid doing anything important on that computer online on the side of caution to avoid any potential virus infection just by visiting a website. because it could be possible that just by visiting a site it might take advantage of a browser flaw to gain access to the system since nothing will be patched at all in relation to flaws related to WinXP in the browser and OS, so if someone can get by the browser and exploit a flaw in the OS, you could have a problem. I am not sure how likely this is to occur, but I would definitely not take the chance if this is used to do anything important online like banking or sign into important sites you care about etc. so basically unless there is a certain software you use that only works on Windows, it's wise to install Linux (which is completely free) on that older system since then you would have a reliable updated machine that's safe to use online and is secure. for example... Mint v21.0-Xfce (which is basically what I got installed on all three of my computers with one of those computers being a high end motherboard board I had since March 2006, as it's basically higher end 2005 motherboard tech, and is limited to 4GB of RAM as that's the motherboards limit) is supported until April 2027 with updates, and like I mentioned, ImgBurn works on this (along with some level of Windows programs(I use Foobar2000 which is a quality music playback/conversion program through Linux to), even though obviously, not all Windows programs will work on Linux through Wine) along with updated versions of browsers like Firefox/Chrome etc. I personally use Firefox as my primary browser and I have Chromium as a backup, but there are other choices like the official Chrome if you prefer that etc. just some thoughts in case you are not aware of this stuff
  4. Re-read the above message and I meant to say -- I had a similar issue yesterday on a burn where I closed the tray and forgot about it for a couple hours before pressing ok to initiate the verify process. Anyhow, just a suggestion that you may want to adjust that pop-up message to suggest waiting for the drive to become idle / stop spinning or whatever before pressing okay to initiate the verify. It may save some coasters and possible headaches in the future for some people. And about XP, it works great for many things and is far more reliable for those things than Windows 10. I have no concern about security.
  5. Unless you must keep WinXP for some reason one should not still be using that at this point as it's not had any security updates since April 2014. Windows 7 lost support in Jan 2020. I suggest putting Linux (Linux Mint v21.0-Xfce) on it as then you would have a secure internet machine and ImgBurn works okay on Linux once setup properly. I can even use KProbe (it's good for checking burn quality of CD/DVD if you got a Liteon drive etc) on Linux to through Wine etc. Linux should not have trouble reading the discs you burned with ImgBurn.
  6. I'd rather not intentionally cause it, but if it should happen I'll try to remember to screen shot. It's not impossible that Windows 10 is contributing to the issue somehow as my other 2 computers are WinXP and Win8.1. The discs nearly always read fine on those 2 computers after these circumstances and I don't recall having this issue burning on them.
  7. Is there any way you can and you're willing to recreate this issue and capture a screen shot of the error message window, if there is one?
  8. The message pops up instantly stating that the tray failed to cycle (because it's a laptop). When I have the issue is when I push the tray back in after the message and do not wait until the drive is 100% idle before pressing OK on that pop-up. I had a similar issue yesterday on one burn where I left the tray open a couple hours before closing it to initiate the verify. That was a rare occurrence though so I do not know if waiting too long will always cause this, but not waiting long enough always does. The verify would not initiate and the disc has not read on this computer even after restarts and inserting another disc before trying again, but it read on my other computer perfectly. It's a very odd phenomenon.
  9. I believe the Playstation 1 also couldn't read CD-RW and it was relatively at the same time as the Dreamcast.
  10. I am pretty sure Dreamcast can't read CD-RW media as all of the games I burned back in the day were on CD-R. p.s.I still got my Dreamcast but it collects dust
  11. You may need RAW mode writing for that... which ImgBurn doesn't support. The image is / was meant for Padus DiscJuggler, but they've shut down, so you probably can't get it now - not legitimately anyway.
  12. Tried burning it again after clearing it without verify checked, and it said it burned correctly, but it gave me the same "insert game disc" message as always when I put it in my dreamcast. Could it be an issue with my system?
  13. To be clear, I've tried to burn many games, and many mirrors of Illbleed, but none have worked, and I assume it's because of this error. I've done everything else I'm supposed to do, watched and read every guide, and it still keeps giving me this error at the very end. I'm at the end of my rope, and just want to play this game. Any help would be greatly appreciated, and if you could dumb it down as much as possible, that would be great too. I'm not very tech literate. Here's the log: I 18:10:45 ImgBurn Version started! I 18:10:45 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 18:10:45 Total Physical Memory: 8,272,216 KiB - Available: 2,368,776 KiB I 18:10:45 Initialising SPTI... I 18:10:45 Searching for SCSI / ATAPI devices... I 18:10:45 -> Drive 1 - Info: HL-DT-ST DVD+-RW GU60N A103-86 (D:) (RAID) I 18:10:45 Found 1 DVD±RW/RAM! I 18:11:08 Operation Started! I 18:11:08 Source File: C:\Users\hazam\Desktop\Illbleed (USA)[RDC].cdi I 18:11:08 Source File Sectors: 343,523 (MODE2/FORM1/2336) I 18:11:08 Source File Size: 802,469,728 bytes I 18:11:08 Source File Volume Identifier: Illbleed-RDC I 18:11:08 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING I 18:11:08 Source File File System(s): ISO9660 I 18:11:08 Destination Device: [0:1:0] HL-DT-ST DVD+-RW GU60N A103 (D:) (RAID) I 18:11:08 Destination Media Type: CD-RW (Disc ID: 97m25s30f, Infodisc Technology Co.) I 18:11:08 Destination Media Supported Write Speeds: 4x I 18:11:08 Destination Media Sectors: 359,847 I 18:11:08 Write Mode: CD I 18:11:08 Write Type: SAO I 18:11:08 Write Speed: 1x I 18:11:08 Lock Volume: Yes I 18:11:08 Test Mode: No I 18:11:08 OPC: No I 18:11:08 BURN-Proof: Enabled W 18:11:08 Write Speed Miscompare! - Wanted: 176 KB/s (1x), Got: 706 KB/s (4x) W 18:11:08 The drive only supports writing these discs at 4x. I 18:11:12 Filling Buffer... (72 MiB) I 18:11:12 Writing LeadIn... I 18:12:06 Writing Session 1 of 2... (1 Track, LBA: 0 - 33599) I 18:12:06 Writing Track 1 of 1... (MODE2/FORM1/2352, LBA: 0 - 33599) I 18:13:56 Synchronising Cache... I 18:14:37 Filling Buffer... (72 MiB) I 18:14:37 Writing LeadIn... I 18:14:53 Writing Session 2 of 2... (1 Track, LBA: 45000 - 343522) I 18:14:53 Writing Track 1 of 1... (MODE2/FORM1/2352, LBA: 45000 - 343522) I 18:31:25 Synchronising Cache... I 18:31:51 Exporting Graph Data... I 18:31:51 Graph Data File: C:\Users\hazam\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_DVD+-RW_GU60N_A103_MONDAY-NOVEMBER-7-2022_6-11_PM_97m25s30f_1x.ibg I 18:31:51 Export Successfully Completed! I 18:31:51 Operation Successfully Completed! - Duration: 00:20:42 I 18:31:51 Average Write Rate: 676 KiB/s (3.4x) - Maximum Write Rate: 710 KiB/s (3.6x) I 18:31:51 Cycling Tray before Verify... W 18:32:09 Waiting for device to become ready... I 18:32:20 Device Ready! I 18:32:21 Operation Started! I 18:32:21 Source Device: [0:1:0] HL-DT-ST DVD+-RW GU60N A103 (D:) (RAID) I 18:32:21 Source Media Type: CD-RW (Disc ID: 97m25s30f, Infodisc Technology Co.) I 18:32:21 Source Media Supported Read Speeds: 4x, 5x, 10x, 16x, 20x, 24x I 18:32:21 Source Media Supported Write Speeds: 4x I 18:32:21 Source Media Sectors: 343,523 I 18:32:21 Source Media Size: 807,966,096 bytes I 18:32:21 Image File: C:\Users\hazam\Desktop\Illbleed (USA)[RDC].cdi I 18:32:21 Image File Sectors: 343,523 (MODE2/FORM1/2336) I 18:32:21 Image File Size: 802,469,728 bytes I 18:32:21 Image File Volume Identifier: Illbleed-RDC I 18:32:21 Image File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING I 18:32:21 Image File File System(s): ISO9660 I 18:32:21 Read Speed (Data/Audio): MAX / MAX I 18:32:23 Read Speed - Effective: 24x I 18:32:23 Verifying Session 1 of 2... (1 Track, LBA: 0 - 33599) I 18:32:23 Verifying Track 1 of 1... (MODE2/FORM1/2352, LBA: 0 - 33599) I 18:33:06 Verifying Session 2 of 2... (1 Track, LBA: 45000 - 343522) I 18:33:06 Verifying Track 1 of 1... (MODE2/FORM1/2352, LBA: 45000 - 343522) W 18:37:06 Miscompare at LBA: 342344, Offset: 2292 W 18:37:06 Device: 0x21 W 18:37:06 Image File: 0x09 W 18:37:06 Total Errors in Sector: 16 W 18:37:06 Note: The drive probably corrected the L-EC Area because it's wrong in the image file. I 18:37:06 Verifying Sectors... I 18:37:22 Exporting Graph Data... I 18:37:22 Graph Data File: C:\Users\hazam\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_DVD+-RW_GU60N_A103_MONDAY-NOVEMBER-7-2022_6-11_PM_97m25s30f_1x.ibg I 18:37:22 Export Successfully Completed! I 18:37:22 Operation Successfully Completed! - Duration: 00:04:52 I 18:37:22 Average Verify Rate: 2,702 KiB/s (13.8x) - Maximum Verify Rate: 4,195 KiB/s (21.3x) Thanks again in advance if you can help me! I'll be incredibly grateful.
  14. ImgBurn won't be shifting anything, so the issue lies elsewhere. Stick to using the special software.
  15. I found the logs! Some data has been redacted to prevent this from showing up in a google search. I 22:32:17 -> Drive 1 - Info: MATSHITA DVD-RAM XXX (E:) (USB 2.0) I 22:32:17 Found 1 DVD±RW/RAM! I 22:33:06 Operation Started! I 22:33:06 Source File: XXX I 22:33:06 Source File Sectors: 2,294,960 (MODE1/2048) I 22:33:06 Source File Size: 4,700,078,080 bytes I 22:33:06 Source File Volume Identifier: NY_00_XXX I 22:33:06 Source File File System(s): Special I 22:33:06 Destination Device: [0:0:0] MATSHITA DVD-RAM XXX (E:) (USB) I 22:33:06 Destination Media Type: DVD-R (Disc ID: TYG02) I 22:33:07 Destination Media Supported Write Speeds: 1x, 4x, 8x I 22:33:07 Destination Media Sectors: 2,298,496 I 22:33:07 Write Mode: DVD I 22:33:07 Write Type: DAO I 22:33:07 Write Speed: MAX I 22:33:07 Link Size: Auto I 22:33:07 Lock Volume: Yes I 22:33:07 Test Mode: No I 22:33:07 OPC: No I 22:33:07 BURN-Proof: Enabled I 22:33:07 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x) I 22:33:08 Filling Buffer... (80 MiB) I 22:33:08 Writing LeadIn... I 22:33:16 Writing Session 1 of 1... (1 Track, LBA: 0 - 2294959) I 22:33:16 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2294959) I 22:41:40 Synchronising Cache... I 22:42:05 Exporting Graph Data... I 22:42:05 Graph Data File: XXX I 22:42:05 Export Successfully Completed! I 22:42:05 Operation Successfully Completed! - Duration: 00:08:58 I 22:42:05 Average Write Rate: 9,106 KiB/s (6.7x) - Maximum Write Rate: 10,857 KiB/s (8.0x) I 22:42:05 Cycling Tray before Verify... W 22:42:13 Waiting for device to become ready... I 22:42:35 Device Ready! I 22:42:36 Operation Started! I 22:42:36 Source Device: [0:0:0] MATSHITA DVD-RAM XXX (E:) (USB) I 22:42:36 Source Media Type: DVD-R (Book Type: DVD-R) (Disc ID: TYG02) I 22:42:36 Source Media Supported Read Speeds: 2.5x, 4x, 6x, 8x I 22:42:36 Source Media Supported Write Speeds: 1x, 4x, 8x I 22:42:36 Source Media Sectors: 2,294,960 (Track Path: PTP) I 22:42:36 Source Media Size: 4,700,078,080 bytes I 22:42:36 Image File: XXX I 22:42:36 Image File Sectors: 2,294,960 (MODE1/2048) I 22:42:36 Image File Size: 4,700,078,080 bytes I 22:42:36 Image File Volume Identifier: NY_00_XXX I 22:42:36 Image File File System(s): Special I 22:42:36 Read Speed (Data/Audio): MAX / MAX I 22:42:37 Read Speed - Effective: 8x I 22:42:37 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2294959) I 22:42:37 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2294959) E 22:42:49 Miscompare at LBA: 0, Offset: 0 E 22:42:49 Device: 0x00 E 22:42:49 Image File: 0x52 E 22:42:49 Total Errors in Sector: 33 E 22:42:49 Failed to Verify Sectors!
  16. I can't include my logs because I forgot to save them. Everything about the burn was normal. There were no errors or anything strange in the logs. The only thing to note was the the disc filesystem was identified as "Special" or something like that. Here's the deal: I have some DVD drives used for game development that have a special firmware. This custom firmware allows them to burn custom discs. While I have some of these discs, they are expensive and way out of production. Every burn costs about $20. Burning with these drives and discs is usually handled by special software. However, all the magic of the drives is handled by the drive firmware. IMGBurn is happy to read and write these discs, as long as the drive has this proper firmware. My issue is that IMGBurn is writing 6 null bytes at the start of every disc. The burn is perfect, except everything is shifted 6 bytes. This is a huge issue since all the hardware to read the discs has hard coded offsets when reading info. Only two discs have been burned so far, but both exhibit this 6 byte shift. I know this is so far outside the scope of IMGBurn support, but any ideas would be a huge help here. Should I try using different burning software to see if it's a quirk with the firmware? Has anybody seen this behavior in imgburn before? I anybody seriously thinks they can help, I have the retail firmware bin files for these drives, the custom firmware bin files flashed at the factory, and the custom disc burning software. PM me.
  17. That's something I didn't think of. On drives that don't auto cycle, ImgBurn will pop up a window saying to manually insert the tray. This window pops up relatively instantly after the tray is ejected. So, there shouldn't be any time for the user to reinsert the tray before the Verify starts.
  18. How are you even telling it to start the verify process? I don’t recall giving the user an option to speed things up. It cycles the tray and then proceeds once the drive thinks it’s ready again. If you have to push the tray in manually, it would just wait longer.
  19. Discs are finalized before Verifies. Otherwise, there is no data. But, if you're getting Verifies that won't start on this laptop but you take those discs to another computer and Verify starts, then the discs are finalized. As to the root issue posted about, I can't see what might cause that. Particularly why the disc won't be recognized even after restarting the laptop. I doubt it would help, but you could try changing the I/O Interface in the Settings and see if you get better results.
  20. Hello, I have had the issue occasionally over the years and I think I discovered the common thread. I always have "verify" selected when I burn a data DVD. I use a laptop so the tray does not close when attempting to cycle between write and verify. If I close the drive tray and wait 20 seconds then the verify always starts successfully and the disc can be read on the laptop after completed. However, if I close the tray and tell Imgburn to start the verify before the disc drive is 100% quiet, then the verify fails to start or gives an error. Also then the laptop refuses to recognize the disc as having data even after restarting the computer and reinstalling drivers for the disk drive. However the disc will almost always (at least 7 out of 10 times) load on my other 2 computers. I am sure the burn is always successful but why won't the data be recognized on this computer, Is the burn not finalized before verifying? I know that I can do the verify as a separate task after, I do not need to select the verify to start immediately after burn and perhaps that's the best way but then I risk forgetting to verify. What is happening? Thank you so much or any enlightenment.
  21. Cancel out of that box and post the log please. It could be that your drive doesn’t support the discs.
  22. Hi I'm facing I/O error while installation, i tried everything to fix this but failed to do so. Someone in the community knows how to fix this? M attaching screen shot for better understanding
  23. The only problematic thing I can see right off the bat may be this line: I 07:03:06 Destination Media Type: BD-R (Disc ID: OTCBDR-002-000) I've never heard of that Disc ID before, so it may be from a no name, cheap manufacturer. Depending on where you are in the world, try the VERBAT-IM discs made by Verbatim. I'd try that first and see if that helps.
  24. I'm having a problem with Bluray data discs always having errors on verify. I have an LG WH16NS40 Bluray rewriter. But I started having the problem with my previous burner, an LG WH14NS40. It started happening after I installed a new motherboard/CPU. I thought the WH14NS40 was failing so I got the WH16NS40, but it had the exact same problem with bad sectors on burns. I have another PC, so I tried both of these drives in it, and I don't get the errors with it. I did try using a different SATA cable, and also tried connecting the drive to a PCI to SATA expansion card (thinking it might bypass the motherboard's SATA controller if the problem was based on that). Also I had an old copy of AnyDVD installed and I uninstalled it, but still get the issue. Also, it seems to read older burned BR data discs with no problem. I'm using Widows 10 22H2 on an Asus TUF GAMING B550-PLUS motherboard (BIOS v2803) with an AMD Ryzen 5 5600. The WH16NS40 drive is firmware v1.05 Since both drives seem to write ok on the other machine, could this be some incompatibility with the motherboard, or some issue with the Windows install? I've exhausted everything I know to do for troubleshooting. ImgBurn Log.txt
  25. I would love it if the batch read feature had the ability to rename the ISOs based on a list in a text file. Discs often have the same or similar names and it makes it nearly impossible to reference back to the original disc if needed. Often time, I want to rename the ISO to the name that was on the disc, but in most cases, the ISO has a generic name like, "DVD_VIDEO" which makes it impossible to figure out which disc it came from without reviewing the content in the ISO and comparing it to the discs.
  26. I'm pretty sure it's just based on the name of the disc. You might be able to force a name and the program will then try to make it unique (add a '(1)', '(2)' etc to it), but don't quote me on that! There's definitely no support for grabbing names from a CSV or whatever.
  27. I've got a VinPower RipBox that I intend to use for batch importing discs. I'm originally used an MF Digital Ripstation to batch import discs which allowed me to name each disc before beginning the batch. It's been a number of years, but I believe I could even set a CSV file as the source for each discs name. Is there any way to automate the naming of disc imports? Or will it always name the files based on the name on the disc?
  1. Load more activity
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.