Activity for Drummer
-
Drummer modified a comment on discussion General Discussion
Hey Ed, The only control I could find on SourceForge was to disallow future email responses to posts, so the user must actually log into SourceForge to post to the forum. This was done earlier today to prevent future email posts. It does nothing to clear up Rob's past thread. If you know how to "clear it up manually" or "create a script to do this" please post detailed instructions . Screenshots of any web actions involved would be most helpful. Please let me know. Thanks, Dave
-
Hey Ed, The only control I could find on SourceForge was to disallow future email responses to posts, so the user must actually log into SourceForge to post to the forum. This this was done earlier today to prevent future email posts. It does nothing to clear up Rob's past thread. If you know how to "clear it up manually" or "create a script to do this" please post detailed instructions . Screenshots of any web actions involved would be most helpful. Please let me know. Thanks, Dave
-
Hey Ed, I agree with you 100%. I'm not sure, but I believe the email reply setting is proper now. Thanks, Dave
-
Hey Ed, I agree with you 100%. However, I haven't found any way to do this within SourceForge. Either manually or with a script. If you know the procedure to manage whether postings include prior responses, please send me details. Thanks, Dave
-
Hey Ed, Have you tried the MX Linux code I posted? Please let me know. Thanks, Dave
-
Hey again Ed, The whole point of the $isopath variable is that the g2wisoboot function searches for the file in the $isopath variable and sets root automatically. This greatly simplifies things for the user, since booting .iso files can be quite challenging. They only need set the four variables, then the g2wisoboot function takes care of setting root, loopback and everything else. Have you tried the MX Linux code I posted? Please let me know. Thanks, Dave
-
Hey again Ed, "Not that your Grub2Win EFI files will be upgraded to level 167." ? This was a typo, should have said "Note" instead of "Not". Fixed this morning and the new level is 168. Over the last couple of days, I have updated g2wisoboot in an attempt to detect these fragmentation errors. g2wisoboot now provides the suggestion to defrag or move the .iso file. Fragmentation errors are now much more common because users don't defrag SSD disks much anymore. Note that even after I defragged the partition,...
-
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> Hey Ed, Try entering the command from a GNU Grub prompt. It fails for me every time. Dave On 3/27/2026 12:28 PM, Ed P wrote: <meta http-equiv="content-type" content="text/html; charset=UTF-8"> "ls ($root)/ISOs/MX*.iso The GNU Grub ls command does not allow * wildcards so it fails." It displays fine in the screen shot I posted. :-) Errors in my config to boot from iso file Sent from sourceforge.net because you indicated interest in...
-
Hey Ed, Couple of observations on your menuentry. ls ($root)/ISOs/MX*.iso The GNU Grub ls command does not allow * wildcards so it fails. You should add a loopback -d loop before your loopback command to prevent duplicates. As to why the file is not found. I have no way to tell without directory listings etc from your system. Hope this helps, Dave
-
Hi again Rob, I'm going to continue this through email instead of web postings. The posting thread is getting too long for me to find messages easily. Also this is very specific to your particular machine. Dave
-
Hi again Rob, After considerable research, I think I have identified the problem. It appears that the filesystem where your .iso file resides is too fragmented for GNU Grub to read. This is a known bug in GNU Grub which hopefully will be fixed soon. I have just uploaded version 3.0.2.3 of Grub2Win which detects this error. Also, the g2wisoboot parameters have changed slightly. I have attached new custom code for you to test. If you still get the kernel read error, you will have to move your .iso...
-
Hey Ed, The 386 messages are from the GNU Grub kernel, not Grub2Win or g2wisoboot. There is a library called i386-efi included in GNU Grub. This is likely because the GNU Grub kernel initializes in 32 bit mode then later switches to 64 bit mode. So some error messages early in the process show as 32 bit. The i386-efi module implies 32 bit operations. The pre EFI library is named i386-pc. 'Nuff said. Dave
-
Hey Ed, The 386 messages are from the GNU Grub kernel, not Grub2Win or g2wisoboot. There is a library called i386-efi included in GNU Grub. This is likely because the GNU Grub kernel initializes in 32 bit mode then later switches to 64 bit mode. So some erroro messages early in the process show as 32 bit. The i386-efi module implies 32 bit operations. The pre EFI library is named i386-pc. 'Nuff said. Dave
-
Hey Ed, The g2wisoboot function was introduced to Grub2Win in 2022, so four years ago. It is documented in the Advanced Topics section of Grub2Win help "ISO File Boot". I just realized that I need to update the Ubuntu URL's in that help text. Will be fixed tomorrow. Thanks, Dave
-
Hi again Rob, I made some changes to your custom code and it seems to work well now. There were a couple of errors in your code. Grub at boot time uses forward slashes / not back slashes \ setparams is a command, not a variable The updated code is attached. You should copy it as your custom code for the ISO. I had to guess at your isopath. The easiest way to set it is to click the green "Select ISO File" button when you edit the custom code. It should set up the isopath properly. Please let me know...
-
Hey again Rob, Thanks, I got the diagnostics and have downloaded the correct .iso from your link. It may take me a day or so to set up your environment and figure this out. I'll keep you posted. Thanks for your patience, Dave
-
Hey again Rob, Thanks, I got the diagnostics and have downloaded the correct .iso from your link. It may take me a day or so to set up your environment and figure this out. I'll keep you posted. Thanks for your patience, Daver
-
Hey Ed, There are several downloads on that page. I want to be sure of the exact URL so as not to waste time on assumptions about which one was actually downloaded. Several desktops are there as well. The diagnostics file typically runs well under 1MB, usually about 200KB. So not a "big Diagnostics file" at all. It takes a minute or two to run the diagnostics and upload. It contains the relevant configuration info to understand where the failure is. Again, I don't want to make assumptions, the diagnostics...
-
Hi again Rob, I really need the full diagnostics as it includes data about your BCD, hardware, EFI listings and Grub2Win configuration files etc. The partition list is useful, but not nearly enough to diagnose your issue. This is crucial to help fix your problem. I need the full diagnostics. I'm not sure I understand about "entering info manually" to run the diagnostics. All that is required is an email address so I can contact you and a couple of lines describing your issue. Your email address will...
-
Hi Rob, Let's see if we can get this resolved. Please run the Grub2Win diagnostics and send them to me. This will give me info on your partitions, hardware configuration etc. I also need a link to the site where I can download the .iso file you are trying to boot. Then I can download the .iso and re-create your environment to assist you. Please let me know. Thanks, Dave
-
Hi Roger, Couple things. Grub2Win version 2.3.2.9 is from April 2022, almost four years ago. Hundreds of things have been fixed since your old release. I suggest that you install the current release, which is 3.0.1.4. If you still have problems, please send me Grub2Win diagnostics. Thanks, Dave
-
Hey Ed, I downloaded the same ISO and booted it via loopback just as you did. It worked for fine me, but I have 64 GB ram on my machine. What issues your out of memory message? GNU Grub or Ubuntu? Still, I don't think Ubuntu should require that much memory. You might want to check out Ubuntu support to research. Dave
-
Hey Ed, I am away on vacation returning January 25. iPad only, no Windows machine or access. So I will look into this when I get home. As far as your EFI directries are concerned, There are literally thousands of .efi modules aout there. Grub2Win can only automatically generate code for the most common ones like Windows boot manager and Opencore. You can always use the "Chainload A File" option to add boot menu entries for your favorite .efi modules. As I said, more details when I return home. Thanks,...
-
Hey Ed, In looking through your notes on this option, I noticed that your tests all had "Secure Boot" disabled. Have you had any success running this with "Secure Boot" enabled in your EFI firmware? I would be very interested if this works for you, as I have long wanted to support "Secure Boot" in Grub2Win. However I have failed so far to find any practical way to support "Secure Boot". All available solutions I have seen require complex manual manipulation by the user, of MOK entries in every user's...
-
Hi, I'm a bit confused. The "grub2win.exe" module never expires. So you should be able to run it forever. If it expires for you, that is a bug I need to fix. Please zip up your old "grub2win.exe" module and upload it here so I can investigate and fix it if needed. The message you gave is from the "G2WInstall.exe" module. This installer module does expire to prevent folks from newly installing old versions of Grub2Win. These old versions sometimes contain bugs that have long since been fixed. I have...
-
Hi, This is a false positive. It happens every few months because Grub2Win, by necessity, does low level system calls, updates the Windows BCD and updates the EFI partition. It has to do these things in order to function. The virus scan companies regard this behavior as suspicious. I report it to the virus scan companies from time to time and they fix it for another couple of months. Then it happens again, as you see. The only way around it is to disable your virus scan real time protection for a...
-
Hi again Graham, I looked through the MBR dumps from your diagnostics. As I thought, the MBR on your disk 0 was overwritten by Kubuntu. You can restore the proper Windows MBR by following this Grub2Win help file: file:///C:/grub2/winhelp/usermanual/Grub2Win%20User%20Manual.html?MBRissues.html Also, refresh the Grub2Win BIOS boot code by clicking the blue "Refresh The BIOS Boot Code" button on the main Grub2Win screen. You may have to repeat this procedure if Kubuntu updates mess things up again....
-
Hi Graham, Please send me your Grub2Win diagnostics. The diagnostics will show each of your two disk's MBR records. With this info, I may be able to offer you a workaround to the problem. Just run Grub2Win and click the blue "Diagnostics" button on the main screen. Please let me know, Thanks, Dave
-
All fixed and Grub2Win is installed now. Thanks, Dave
-
I am contacting you privately with instructions. Dave
-
Hi, This issue is fixed in Grub2Win version 3.0.0.6 Build 1778 or higher. It was triggered by changes in the way Windows 11 version 26200 processes certain files. Thanks, Dave
-
Hi Jeff, You should understand that Grub2Win simply loads the Chrome or Brunch kernel into memory. Then Grub2Win is removed from memory. Once you select Chrome or Brunch, the Chrome or Brunch code is in control of your machine. Grub2Win is long gone. You must seek support from the Chrome or Brunch site where you downloaded their code. Thanks for understanding, Dave
-
Hi, This may be caused by an incompatibility with the newest AutoIt version 3.3.18 compiler. AutoIt is used to generate the Grub2Win .exe files. Some older and BIOS machines have problems with 3.3.18 generated code. I am now compiling the Grub2Win Legacy code using the previous AutoIt 3.3.16 compiler. Please download the latest Grub2Win Legacy version 1.4.3.5 build 1004 or higher. It contains the code from the older 3.3.16 compiler. Available here https://sourceforge.net/projects/legacy.grub2win.p/files/...
-
Hi, This may be caused by an incompatibility with the newest AutoIt version 3.18 compiler. AutoIt is used to generate the Grub2Win .exe files. Some older and BIOS machines have problems with 3.18 generated code. I am now compiling the Grub2Win Legacy code using the previous AutoIt 3.16 compiler. Please download the latest Grub2Win Legacy version 1.4.3.5 build 1004 or higher. It contains the code from the older 3.16 compiler. Available here https://sourceforge.net/projects/legacy.grub2win.p/files/...
-
Hi, It seems you are OK for now. As long as the installer is SSL signed by me. Grub2Win detects and deletes these out-of-date modules and installers downloaded from the fake site. Beware though, The fake site might start offering malware at any time. This is beyond my control. I have initiated a legal process against the site. The hosting company has been served with a takedown notice. This process can take several months, particularly when the host is in another country. Dave
-
* This is a major release of Grub2Win * Version 3.0.0.1 Grub2Win will now support Windows 11 and Windows 10 systems exclusively. All systems must run 64 bit EFI firmware to be supported. For these modern systems, the latest Grub2Win can be downloaded here: https://sourceforge.net/projects/grub2win/ ******* I realize the many users still run older BIOS firmware and even 32 bit systems. For these older systems, I created Grub2Win Legacy. This allows Windows 7, Vista, Windows 8 and Windows XP to run...
-
* This is a major release of Grub2Win * Version 2.0.0.1 Grub2Win will now support Windows 11 and Windows 10 systems exclusively. All systems must run 64 bit EFI firmware to be supported. For these modern systems, the latest Grub2Win can be downloaded here: https://sourceforge.net/projects/grub2win/ ******* I realize the many users still run older BIOS firmware and even 32 bit systems. For these older systems, I created Grub2Win Legacy. This allows Windows 7, Vista, Windows 8 and Windows XP to run...
-
Hi Sarah, I have not been able to recreate this behavior on any of my systems. It is possible that there is an unusual entry in your Windows BCD. Please send me your Grub2Win diagnostics. The diagnostics include information about your hardware and BCD configuration. Once I have your diagnostics, I can look into this. Thanks, Dave
-
Hi again, There is indeed a problem with this script. I'm a bit embarrassed that this bug has been around for so long. Must be that very few people used the script, so I was not aware of the bug. Anyway I've revised the script, the new one is attached. It will be included in the next release of Grub2Win. Please give it a try and let me know. Thanks, Dave
-
Hi, The script is found in file C:\grub2\winsource\xxgrubsetup.txt You can simply edit the script and add the quiet parameter. See this Grub2Win help file for details. file:///C:/grub2/winhelp/usermanual/Grub2Win%20User%20Manual.html?AutomaticSetupandParms.html Please let me know if this works for you. Thanks, Dave
-
Hi, Yes, this is possible, but not recommended. It involves updating the Windows C:\grub2\grub.cfg file from Ubuntu. You run the risk of creating an unbootable system. Realize that Grub2Win updates the C:\grub2\grub.cfg file every time you run Grub2Win. So any updates you do from Ubuntu may be overwritten. That said, you can edit the C:grub2\grub.cfg file and search for the "set default=" line. Then update the number to whichever menu entry you wish. Again, this is dangerous, so be careful. I hope...
-
grub2win.com is not authorized to offer Grub2Win for download. It is probably a scam site. The site is currently registered in Reykjavík Iceland by a hosting company - spaceship.com. I have tried multiple times to contact them. They have ignored all of my requests. grub2win.com contains documentation with glaring errors, and I fear, malware. The module they offer for download is my signed copyrighted exe file. The file is several months old. You should not download code from grub2win.com. Dave
-
**grub2win.com is not authorized to offer Grub2Win for download. It is probably a scam site. ** The site is currently registered in Reykjavík Iceland by a hosting company - spaceship.com. I have tried multiple times to contact them. They have ignored all of my requests. grub2win.com contains documentation with glaring errors, and I fear, malware. The module they offer for download is my signed copyrighted exe file. The file is several months old. You should not download code from grub2win.com. D...
-
Hi, I don't believe either of these things are feasible. Here are the reasons: "Please add traditional Chinese interface ..." This would require a massive rewrite of the Grub2Win code. Probably several months of work. It would also require the continuing services of a translation team. I am the single developer and maintainer of Grub2Win. So I don't have the translation resources or the spare time to do a complete rewrite. "Please add Portable version ..." Grub2Win updates many files in various locations...
-
Hi Helmut, Thanks for the info. I'm glad you were able to work around the problem. I would like to better understand what caused this issue. Would you mind sending me your Grub2Win diagnostics file? The diagnostics file contains information about your hardware, BCD, EFI files and Grub2Win configuration. To get the diagnostics file, run Grub2Win and click the blue "Diagnostics" button. Fill in the required information and click "OK" to run the diagnostics. The diagnostics run usually takes 1 - 2 minutes....
-
Hey folks, Unfortunately there is little I can do about this. There is no workaround. Defender does not like programs that manipulate the BCD, EFI or firmware entries. These are things that Grub2Win must do to function properly. I contact Microsoft support frequently on this issue. In this case I cannot, because Microsoft requires information from the actual failing machine. Mine is not failing this time around, so I can't submit a report, since I don't have the data.. Because your machines are failing,...
-
Hi again, I sent you a message with a possible fix. But I never heard back from you. Is Grub2Win working on your system now? Please let me know. Thanks, Dave
-
Hi Franz, I need more detail about your "accident" to better understand. Was your PC powered down or rebooted while the Grub2Win setup was running? What version of Windows? 10, 11, 7 or XP? EFI or BIOS firmware? It makes a big difference in the boot process. It may be that boot files were partially written or corrupted if there was a sudden boot or power event while the setup was running. This may have ruined the Windows BCD or boot files. You should try booting your Windows install media and running...
-
Hi Franz, I need more detail about your "accident" to better understand. Was your PC powered down or rebooted while the Grub2Win setup was running? What version of Windows? 10, 11, 7 or XP? EFI or BIOS firmware? It makes a big difference in the boot process. It may be that boot files were partially written or corrupted if there was a sudden boot or power event while the setup was running. You should try booting your Windows install media and running the Windows startup fix or recovery procedures....
-
Grub2Win is an open source project. This means that the source code is freely available here at SourceForge and can be freely distributed. You are also free to copy, customize and compile the source code to create your own .exe modules. That said, my compiled, signed .exe files are subject to copyright and may not be distributed without permission. This restriction applies the grub2win.exe, setup.exe and G2WInstall.exe modules. Also to any compressed files that contain these modules. SourceForge...
-
Grub2Win is an open source project. This means that the source code is freely available here at SourceForge and can be freely distributed. You are also free to copy customize and compile the source code to create your own .exe modules. That said, my compiled, signed .exe files are subject to copyright and may not be distributed without permission. This restriction applies the grub2win.exe, setup.exe and G2WInstall.exe modules. Also to any compressed files that contain these modules. Several sites...
-
Grub2Win is an open source project. This means that the source code is freely available here at SourceForge and can be freely distributed. You are also free to copy customize and compile the source code to create your own .exe modules. That said, my compiled, signed .exe files are subject to copyright and may not be distributed without permission. This restriction applies the grub2win.exe and G2WInstall.exe modules. Also to any compressed files that contain these modules. Several sites are distributing...
-
Grub2Win is an open source project. This means that the source code is freely available here at SourceForge and can be freely distributed. That said, the compiled, signed .exe files are subject to copyright and may not be distributed without permission. This restriction applies the grub2win.exe and G2WInstall.exe modules. Also to any compressed files that contain these modules. Several sites are distributing these compiled, restricted files without permission. Beware these sites. They my be distributing...
-
Hi, Please download, unzip and run this file. https://sourceforge.net/projects/sourcecode.grub2win.p/files/GetSysInfo.zip/download It will create a diagnostic file with information about your hardware and BCD configuration. Upload or send the file to me and I will have a look. Thanks, Dave
-
Hi again Jean, After researching your laptop specs, it appears that this motherboard contains BIOS, not EFI firmware. If that is the case, I suspect that the Xubuntu install overlaid the MBR on your boot disk. This is a very old motherboard, circa 2009, so I cannot be sure of the firmware. You may have to boot from your Windows 10 Pro install media and run the system repair to restore the proper MBR. Pleas let me know of your progress. Thanks, Dave
-
Hi Jean, Please run the Grub2Win diagnostics by clicking the blue "Diagnostics" button near the bottom of the main Grub2Win screen. Then send me the diagnostics file. I need the diagnostics to understand your specific hardware and Grub2Win configuration. Thanks, Dave
-
Hey Ed, I'm contacting you directly for further discussion of this. Thanks, Dave
-
Hey Ed, Again, the MBR2GPT utility's sole purpose is to convert from MBR to GPT. The resulting GPT disk is useless since XP will not boot from a GPT disk. I have tried, it doesn't work. XP simply says that no boot media is found. Black screen. Dave
-
Hey again Ed, I looked over the GPT utility documentation and I don't see where this is possible. At least on disk drives such as Godan is using as opposed to USB sticks. Please show me the GPT utility command syntax you are referencing that adds additional MBR 's to a disk drive that is bootable by XP. An example of the full command would be helpful. Let me know. Thanks, Dave
-
Hey Ed, This old utility is to convert MBR disks to GPT. So you wind up with a GPT style disk drive. Thing is, Windows XP cannot boot from a GPT drive. It can only boot from MBR style disks. So this utility will not solve Godan's issue. Thanks, Dave
-
Hi Godan, This would be extremely difficult, if not impossible. The issues are these: The MBR code must be on disk 0 for BIOS firmware systems. There can only be a single MBR on that disk. The MBR code is different for Windows 10 and XP systems. They cannot both exist on the same disk. Both the XP and Windows 10 BIOS bootloaders expect the Windows directory to be on disk 0 partition 1. Not shareable. This would cause many conflicts and compatibility problems as both Windows installations would have...
-
Hey Ed, As I have mentioned several times, these are false positives. They happen because Grub2Win performs several system calls necessary to scan the disk partitions, update the EFI directories and set the firmware boot order. There is no other way, I'm aware of, to perform these functions. Several virus scan packages regard these calls as suspicious and incorrectly show a false positive. They often quarantine the file in question. There is no virus or malware in Grub2Win. You can examine and compile...
-
Hey Ed, As I have mentioned several times, these are false positives. They happen because Grub2Win performs several system calls necessary to scan the disk partitions, update the EFI directories and set the firmware boot order. There is no other way I'm aware, of to perform these functions. Several virus scan packages regard these calls as suspicious and incorrectly show a false positive. They often quarantine the file in question. There is no virus or malware in Grub2Win. You can examine and compile...
-
Hi again, If you would like the logo to display, add the Linux parameter "splash" along with "quiet". You should also remove the "nosplash" parameter if it is there. Please let me know if this works for you. Thanks, Dave
-
Hi, You should update the Mint menu entry. Run Grub2Win and click the "Manage Boot Menu" button. Then click the entry for your Linux Mint. This should take you to an orange edit screen where you can update the Linux boot parms. Replace the "verbose" parm with "quiet" Then click OK and run Grub2Win to completion. Please let me know if this works for you. Thanks, Dave
-
Over the last few days, there have been several false positive virus warnings from Microsoft Security (Defender). There is no virus. Anyone can examine and compile the source code here at SourceForge. In addition, the compiled code is SSL signed, so it cannot be altered or corrupted. Hopefully, Microsoft will correct this situation shortly. In the meantime, there is a workaround. You can exclude the Grub2Win directories from Defender virus scan. The path to the exclusion settings is Windows Security...
-
Über Google Übersetzer Hallo, Dies ist ein Fehlalarm. Solche Fehler treten gelegentlich auf, insbesondere bei Defender. Sie können den Grub2Win-Quellcode hier auf SourceForge überprüfen, um sicherzustellen, dass er virenfrei ist. Der Code ist SSL-signiert und kann daher nicht verändert oder beschädigt werden. Microsoft wird das Problem voraussichtlich in einigen Tagen beheben. In der Zwischenzeit können Sie die Echtzeitprüfung von Defender für einige Minuten deaktivieren. Nachdem Sie Grub2Win installiert...
-
Hey Ed, I'm confused. "No AV apps" so how is the virus detected? Please send a screenshot of the error. Thanks, Dave
-
안녕하세요, 오류 메시지에서 확인한 내용으로만 조언을 드릴 수 있습니다. 표준 Microsoft 디스크 호출은 디스크의 섹터 0을 읽으려고 할 때 오류 코드 87을 수신합니다. 이는 유효한 호출이며 하드웨어에서 오류 코드를 수신해서는 안 됩니다. 이는 디스크 또는 컨트롤러 하드웨어 문제로 인해 발생할 수 있습니다. Windows 디스크 드라이버 문제일 가능성도 약간 있습니다. 시스템을 원격으로 진단할 수 없습니다. 하드웨어 공급업체나 Microsoft에 문의하여 컴퓨터에 대한 지원을 받아야 합니다. Linux gdisk 유틸리티를 사용하여 GPT 파티션 테이블을 검사하거나 복구할 수 있습니다. https://www.youtube.com/watch?v=v9PU2mnNoA0 도움이 되기를 바랍니다. Dave Hi again, I can only advise you from what I see in the error messages. The standard Microsoft disk calls...
-
안녕하세요, 귀하의 경우, 이는 실제 하드웨어 오류인 듯합니다. Grub2Win은 표준 Microsoft Win32_DiskDrive 호출을 사용하여 디스크와 파티션을 검사합니다. 디스크 0의 섹터 0에 대한 디스크 읽기 호출이 심각한 오류를 반환합니다. 디스크 0은 SD 리더가 아닙니다. NVME SSD입니다. Microsoft는 드라이브에서 chkdsk 유틸리티를 실행할 것을 제안합니다. 이 디스크의 GPT 파티션 테이블에도 문제가 있을 수 있습니다. 이것이 귀하에게 효과가 있는지 알려주세요. 감사합니다, Dave Hi, In your case, this appears to be an actual hardware error. Grub2Win uses standard Microsoft Win32_DiskDrive calls to examine your disks and partitions. The disk read call for sector 0 of your disk 0 returns...
-
Hey again Ed, Grub2Win diagnostics please. With the CD plugged in. The diagnostics can display info on about 280 partition types. Although it cannot read all of them, it can at least give us some insight as to the nature of the drive and its partitions. Thanks, Dave
-
Hey Ed, So how is the partition on your USB drive formatted? What filesystem. Please plug the drive in, run current Grub2Win diagnostics and send them to me. Then I can hopefully see the partition block 0 format as well as the hardware info. Please let me know. Thanks, Dave
-
Hi again, So is your problem resolved? It seems so. Please let me know. Thanks, Dave
-
Hey Ed, From his earlier posts, the production .exe is running OK. No other reports of this issue. I have no idea what his customization is for. Dave
-
Hey Ed, Yeah but, the grub2win.exe he generated does not work. It crashes. So he can't run diagnostics, because it crashes. So we must use the normal, production grub2win.exe to run the diagnostics. Dave
-
Hi, I need your Grub2Win diagnostics to troubleshoot this issue. Please run the diagnostics from the normal installed Grub2Win exe, Not the one you built. Please let me know. Thanks, Dave
-
Hi again, OK. I believe that I finally have this fixed. It involved an unusual condition where the disk scan buffer was stale. This affected only very specific motherboards, that is the reason it was difficult to diagnose. Anyway, please download and install version 2.4.2.2 Build 1715 or higher. Try it without the flash drive plugged in. Please let me know if this works for you. Many thanks for your help, patience and understanding, Dave
-
Hi again, I prefer to fix the problem rather than relying on random old releases that may or may not work. I am actively looking into this issue, which I suspect is some sort of unusual disk controller situation. It seems to occur very rarely on a few specific motherboards. I just uploaded a new refresh of version 2.4.2.2 with a build number of 1714. This build includes some additional code which checks disk buffers. Please download and install 2.4.2.2 build 1714 or higher to see if this resolves...
-
Hi, No, the current version is the only one that should be installed. This is both to prevent malware and the rediscovery of bugs that have already been fixed. Thanks, Dave
-
Hi, I sent you an email with instructions to trace this error. Did you receive my email? Please let me know. Thanks, Dave
-
こんにちは。 この問題を修正できる可能性のある Grub2Win の新しい更新版をアップロードしました。 バージョン 2.4.2.2 ビルド 1713 以降をダウンロードしてインストールしてください。 これで問題が解決するかどうかお知らせください。 ありがとうございます。 Dave Hi, I just uploaded a new refresh of Grub2Win that may fix this issue. Please download Version 2.4.2.2 Build 1713 or higher and install it. Let me know if this works for you. Thanks, Dave
-
Google 翻訳経由 こんにちは、 診断結果を確認しました。 完全に正常なようです。 システムには 2 つのディスク ドライブと 7 つのパーティションがあります。 Grub2Win は標準の Microsoft Win32_DiskDrive コマンドを使用してディスクにアクセスします。 診断結果が今日実行されたことに気付きました ディスクとパーティションは今日正常でした。 投稿されたエラー メッセージは数日前の 2 月 24 日のものです。 これらの日付の間にこの問題の原因となる何かが起こりましたか? パーティションが変更されたか、ディスク ハードウェアが再配置されましたか? ハードウェアまたはパーティションの破損状況がこのエラーを引き起こした可能性があります。 報告された動作に関する他の報告は受けていないため、困惑しています。 お知らせください。 ありがとうございます。 Dave Hi, I looked through your diagnostics. They appear completely normal. There are 2 disk drives and 7 partitions...
-
Hi Jose, What is the app that created the picture you posted here? Please let me know. Thanks, Dave
-
Hey Ed, Julian date typo fixed. Thanks, Dave
1 >
