Jump to content

All Activity

This stream auto-updates

  1. Yesterday
  2. Ah, I was not aware the Optiarc was still in manufacture. I used to love those. They were my drives of choice until they disappeared, as far as I could tell. I use BD burners now, so I wouldn't get an Optiarc, but it's nice to hear they still make those. Thanks for pointing out about the Pioneer 213 line coming out. I was about to try a 212 again to see if Pioneer had fixed the glaring issues with the drives/firmware that turned me off of their models. But, if a new one is coming out possibly next month, I'll wait to see if a 213 is available.
  3. Does this drive not work? It says the enhanced model of this vinpower drive supports scanning. https://www.vinpowerdigital.com/products/wh16ns58dup
  4. The Pioneer BDR-S12XLT is the premium branded retail version with glossy piano black front bezel and uses additional Pioneer premium features like honeycomb embossed anti-vibration drive casing, anti-dust design and sealing, etc. The BDR-212EBK is the branded regular OEM grade model. Both were concurrently available models within the Pioneer "12" series ODD product line, which have now been discontinued. The 13-series models will soon be launched by 2021 mid-December in Japan. Most 12-series inventory are now mostly depleted. If you can, wait for the 13-series models. Based on past models, you can probably expect a BDR-S13XLT, a BDR-213EBK (the E-suffix appears to denote European market model), BK-suffix denotes black coloured bezel, because Pioneer used to offer several bezel colours, including black, white and a 3rd colour which I don't remember at the moment. There will likely also be a BDR-213DBK OEM unbranded model, which is a BD (non-BDXL) only model, where the D-suffix denote deletion of the DVD-RAM writing function. For North American, there should be a BDR-2213 branded retail bundle with BD software. Pioneer so far has announced two domestic Japan models for the 13-series, an ultra premium model and a regular branded model. I personally use multiple Pioneer 09-series BDXL writers and their performance and consistency have been superb and predictable so far. I also recently installed a Pioneer BDR-S12XLT and will soon find out if this drive will perform as expected. An alternative could be the Pioneer BDR-212V BD writer (non-BDXL) whose V-suffix denote the DVD firmware portion optimization by Vinpower for improved DVD media writing and overburn. This drive is fairly reasonably priced. Vinpower is a California based American company who manufactures and distributes ODD duplication towers, as well as continuing Sony-NEC's Optiarc DVD ODD brand (with technical consultation with Sony), Plextor brand and Piodata (having taken over Pioneer's previous DVD line), all of these DVD drives which are now OEMed by Philiips-Lite-On in Taiwan.
  5. Does anyone know which brand / models of BD or BDXL readers or writers use the Mediatek chipset? It seems that Philips-Liteon has discontinued their internal BD reader drives, Sony apparently used to use Mediatek chipsets but have been out of the ODD market for years now. Samsung doesn't appear to make any internal BDXL drives, and Hitachi-LG BD/BDXL ODDs don't appear to use the Mediatek chipset, as I recently tested one from Hitachi-LG and it did not work with Opti-Drive Control utility to test BD LDC/BIS rates. Pioneer BDXL writers allow for Opti-Drive Control disc quality tests for DVD media, but not BD/BDXL media.
  6. Last week
  7. it boots and I now have a fully automatic VM creation script using powershell and ImgBurn. Thank you for the amazing tool
  8. Ok, maybe it was the load segment value was throwing it off before. Most other bits get noticed and corrected by the program when it detects you want to build an OS installation disc. As you're using etfsboot.com, it doesn't look like you're building a UEFI bootable disc, it looks like a legacy bios one. This is the same issue covered a couple of days ago in this thread... But if it boots for you, I guess it's all good and your VM has handled it.
  9. google was useless for me too and my hyper-v vm is running UEFI. i found out the correct command was as follows: & 'C:\Program Files (x86)\ImgBurn\ImgBurn.exe' /MODE BUILD /BUILDOUTPUTMODE IMAGEFILE /SRC "C:\ISO\Source\" /DEST "C:\ISO\.iso\test121" /VOLUMELABEL "test121" /VOLUMELABEL_UDF "test121" /START /CLOSE /NOIMAGEDETAILS /ROOTFOLDER YES /PRESERVEFULLPATHNAMES NO /OVERWRITE YES /BUILDINPUTMODE STANDARD /BOOTEMUTYPE 0 /BOOTIMAGE C:\ISO\Source\boot\etfsboot.com /BOOTDEVELOPERID "Microsoft Corporation" /BOOTLOADSEGMENT 07C0 /BOOTSECTORSTOLOAD 8 /FILESYSTEM "UDF" Never seen "CDBOOT: Cannot boot from CD - Code: 3" before only 5, 4 and 1 Thank you for the quick reply, if you want any information on the automation script or the use of your product feel free to ask. kind regards Necis Orcus
  10. Google doesn't throw up a whole lot when searching for that error. Is your vm in UEFI or legacy bios mode? I assume that if you follow the OS installation disc guide in the Guides forum and actually do it via the GUI, you get the same result?
  11. i get the following error code on vm boot using a powershell script "CDBOOT: Cannot boot from CD - Code: 3" my current powershell command for creationg the .iso file is as follows: ($newN is a varible made in the script that choses its name based on input | Error continues with preset names) & 'C:\Program Files (x86)\ImgBurn\ImgBurn.exe' /MODE BUILD /SRC "C:\ISO\Source\" /BUILDOUTPUTMODE IMAGEFILE /DEST "C:\ISO\.iso\$newN" /VOLUMELABEL $newN /START /CLOSE /NOIMAGEDETAILS /ROOTFOLDER YES /PRESERVEFULLPATHNAMES NO /OVERWRITE YES /BUILDINPUTMODE STANDARD /BOOTEMUTYPE 0 /BOOTIMAGE C:\ISO\Source\boot\etfsboot.com /BOOTSECTORSTOLOAD 8 Please ask away for any information needed or wanted. \:)
  12. Earlier
  13. Yes... I'll try this config and if doesn't work, I'll buy a new drive. Thanks, bro
  14. I'll try this tomorrow! I use burnmax before burn the dvd's. It is The same thing? Thanks for help
  15. Thanks for all the assistance. I've been able to create a bootable ISO using ImgBurn. Now I have to try it again with the Enterprise edition of Windows 11.
  16. You can also make a little registry change during the installation. That’s what I did the other day when making a VMware workstation vm of it.
  17. If you just try to circumvert Win 11 restrictions, use this tool to rebuild the ISO https://forums.mydigitallife.net/threads/win-11-boot-and-upgrade-fix-kit.83724/
  18. Tried those parameters (sectors to load =4 before I tried your suggestion of 1). It worked, with your suggestion of 1 sector to load. Of course, installation failed, but I think that I can handle (vTPM VM encryption, etc.) Thank you!
  19. That may have been the reason I couldn't get it to work all those years ago. I knew the Guide was a tad bit out of date and didn't think it might be a UEFI thing.
  20. The guide. Try with platform ID set to UEFI and for the boot image, select \efi\microsoft\boot\efisys.bin Sectors to load is 1 I think.
  21. Ah! Does the product need an update or does the guide need an update (or both)?
  22. The reason I asked is that those guides predate uefi (mainstream at least) and are meant for bios boot.
  23. Haven't read or created a disc in years. Tossed out my unopened DVD writables a few months ago. Probably too old to be useful, even if I needed them. Backup is to a pair of Synology NASes (full backup --10.1TB -- every six hours) and to CrashPlan and Google Drive (in near-real time).
  24. It's up to the user. You get lifetime, as far as I'm aware, upgrades for $20, but if you never use the software again, it can be pretty hard to justify the $20 for a one time use. I use it every time an update to Macrium Reflect comes out, as well as at the start of each new year when I move the monthly file backups to bootable Reflect recovery media with the image files on them. So, for me it was worth it.
  25. As far as I am aware, Windows 11 requires UEFI boot. The VM is configured for UEFI. That's actually the default these days. Regarding UltraISO, it looks like it makes it easy to just delete a file from an ISO and save the ISO back, but the trial has a limit of 300MB, so I can't verify that it actually works. I am on the fence for the $20. I might never use it again except for this one time.
  26. Do you use bios boot or uefi? The iso you build needs to match what your vm is expecting.
  27. As I said, I followed the guides a long time ago and never could get a bootable Windows disc. The ISO's when burnt to optical discs would never boot. Tried to get the same with Acronis True Image bootable discs. Attempting to build new discs never worked, which is why I resorted to UltraISO to inject/remove new files into bootable disc ISO's. I'd use ImgBurn to read the bootable discs to ISO and then UltraISO to edit the ISO's and ImgBurn to then, again, burn the UltraISO ISO's. to disc.
  28. I found the guide. Not sure how I missed it last night when was looking. I followed the easy directions to a T other than selecting ISO as output. Unfortunately, the ISO doesn't seem to be bootable. At least the VMware (ESXi) Remote Console is unable to boot a new VM from it.
  1. Load more activity
×
×
  • Create New...

Important Information

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