Jump to content


  • Content Count

  • Joined

  • Last visited

About Johnhc

  • Rank
    ISF Newbie
  1. Thanks, LIGHTNING UK! I'll use this the next time instead of changing monitor cables. Enjoy, John.
  2. Thanks, LIGHTNING UK! I see the same thing. The first time, I restored it and all was OK. Somehow it got minimized again and when I set View-Log, it flashes in the lower left corner, but I cannot find it. I use 3840x2160 resolution (on Display Port), so I tried various resolutions and scales and still could not restore it. Doing an Uninstall/Install does correct the problem, but the window keeps disappearing (I swear I did not do it) and I cannot find it. I'll keep messing with it. Thanks and enjoy, John. EDIT: I did some experiments and with an HDMI connection, the Log window still gets lost, but by changing the scale to 100% (instead of 150%), the window appears in the lower left. This is not so certain with DP connection. Sometime 100% works and sometime not. Why do I not see a second icon on the Taskbar for the Log? If there is a Registry key with the Log window position, please post it so I can muck with it when my Log window gets minimized and lost.
  3. LIGHTNING UK! I have attached ImgBurn exported keys. Thanks and enjoy, John. ImgBurn.reg
  4. Thanks, dbminter. No, I mean the second window that normally opens when I open ImgBurn. View-Log is checked and checking it again just gets me the "head in the sand" response. The log file is found under Help. Enjoy, John. EDIT: OK, I found it. It must have been Minimized. So now when I click View-Log, I see a very small window flash in my lower left screen but it does not stay.
  5. LIGHTNING UK! My problem has nothing to do with ImgBurn or how I create my ISO. There is something in the AMD RAID Option ROM or Windows, that is causing the failure because I am using a 16 GB USB stick. No matter how I try to install the RAID drivers once I boot my 16 GB USB stick, it fails. So sorry to bug you. I do have a question. At several times I have lost the Log file and I did NOT close it. Also I cannot figure out how to get it open again. View-Log is checked and checking it again just gets me the "head in the sand" response. How do I get the log back? Thanks and enjoy, John.
  6. Thanks, LIGHTNING UK! I agree that 4.5 GB is a weird number - 4 GB maybe. I have been trying various BootOrder file contents with no luck. If you have any suggestions I am very willing to test. Thanks and enjoy, John.
  7. Thanks for your reply, LIGHTNING UK! Here is a screenshot of that tab. When I found that ImgBurn did not work for me I started trying to understand oscdimg.exe. I have not accomplished that yet, but found that it said: "For images larger than 4.5 GB, you must create a boot order file to make sure that boot files are located at the beginning of the image." I had tried to use oscdimg.exe without the BootOrder file and that did not work. I tried with the file presented here and had a error saying boot\memtest.efi could not be found and was being skipped. I have a thread open in the TechNet forum to see if I can get a up to data W10 BootOrder file. My image is greater than 10 GB. Does ImgBurn use a BootOrder file and if so can you please tell me where to find it? I put Strange in the title because I certainly do not understand. I have tried many things with no luck. Thanks and enjoy, John.
  8. Double post - can't delete - sorry.
  9. Sorry, LIGHTNING UK!, I should have posted with my original. Here it is. Thanks and enjoy, John. ImgBurn.log
  10. I have an ASRock X399 board with NVMe RAID support, but it requires pure UEFI support. I have gone into the UEFI (BIOS) and set CSM (Compatibility Service Module) to Disabled (UEFI only). When I boot into the Boot Menu (F11) I am shown only UEFI devices. I have used ImgBurn to create an ISO for many years and tried for a UEFI bootable ISO. I use Rufus to write the ISO to a USB stick and it boots fine. The strangeness occurs when I get to the W10 "Install Where" menu. I have to use "Load Driver" to be able to see the RAID drive properly. The loading of the drivers (3) seems to go fine, but Setup never displays the RAID device properly. I used an ISO DLed from MS and written to a USB by Rufus and it works fine. I do not know what additional information may be needed, but please let me - will keep an eye on the thread. I searched for information on settings for making a UEFI ISO and found none. Thanks and enjoy, John.
  11. LIGHTNING UK!,, I have created an ISO with ISO9660+UDF and DOS. It boots and goes through text mode 'copy files' with no problems. The label is as I desire and the file/folder name case is also. I am making a new source now to install on my HW. I expect it to work OK. Thanks so much for your patient help. I really appreciate it and ImgBurn. I will reply again if I have any further problems. Thanks, John.
  12. LIGHTNING UK!, thanks for your reply. I will try ISO9660+Joliet with DOS, but not until tomorrow. I am currently on my new HW. I did see your earlier suggestion, but in my defense, please see my reply in post 4. I did notice that the label on my DVD was the shorter one (Joliet) not the one I really wanted - correctable? Thanks again - will report my results. Enjoy, John.
  13. LIGHTNING UK!, I have recreated the problem. I went back to DOS and corrected the problem. I also tried ISO9660+Joliet and ASCII, which gave me the mixed case I wanted but had the 'cannot find cdrom.sys' problem. I have returned to mkisofs to created ISOs. I would much prefer to use ImgBurn, so let me know if you have a suggestion for a work around or experiment you would like me to run. Thanks, John.
  14. LIGHTNING UK!, I do not know IsoBuster, but I opened ImgBurn on the failing ImgBurn ISO and it says it is "ISO (Bootable)" , on the mkisofs ISO "ISO (Bootable), Joliet" I have not run this experiment but will. I had to move my source because I needed to make some changes. I will need to create an ISO on the moved folder and see if it fails with ASCII, then try DOS. The reason I have not tried this is because I really don't want all upper case file/folder names but will if it will help to get at the problem. When I started using ImgBurn, I used all the recommended and never had a bad ISO. I will edit this reply when I have some results. Thanks much, John. EDIT: I am unable to recreate the error, even with the copy of folder. This is how evanescent the problem is. I will use ImgBurn for my ISOs and if the error does come back, I will run some experiments. Thanks much.
  15. ianymaty, thanks much - missed the Tools path. LIGHTNING UK!, thanks, but I do not know what mkisofs.exe uses. It is an option in nLite (used to make Windows installations). The Default one in nLite started making bad ISOs (missing file/folders) when my source got large (>2.6 GB). I do not understand what you are suggesting here as far as how I use ImgBurn. What scares me is that some ISOs I create are just fine and others display the 'cdrom.sys missing' message. I do not know what is the reason for this sometime behavior. Thanks, John.

Important Information

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