Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 



mariella

Member
  • Content count

    8
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mariella

Profile Information

  • OS
    Windows 10 x64
  • Country
  1. WinNTSetup v3.8.8

    Here it is (dumped output attached). Anyway, before posting on this thread, I had already checked with coreinfo and I saw that PAE, NX and SSE2 were OK, so that the CPU should have to be compatible with Win 8, I guess ... On the other hand, as i said, I installed and ran it on the same machine, even if this is not surely a proven proof! coreinfo.txt
  2. WinNTSetup v3.8.8

    Hi JFX, the first suggestion (for ISO mount) have worked nicely. For the red icon, it comes up when I try lo load the 8 Enterprise evaluation and and it says "CPU Win 8 not ready". This is strange though, because I've tried successfully to install different version of Win 8 ! mariella
  3. WinNTSetup v3.8.8

    Hi JFX, at first I wolud like to congratulate you on your fantastic WinNTSetup tool, which I've known through the Wimb's thread "VHD_W8_Compact - Make Mini 8". I'm making some experimentation with your tool (last 3.7.2 stable version) by building a "compact" Win8.1 on a penflash but, while building the vhd image, I was always constrained to load the related install.wim as source, because I always was not able to load the .iso image (R-click on Source). Whenever I choose the iso loading procedure (R-click), nothing seems to happen after I select the ISO from the file dialogue window and click Open. I've made a lot of trials (even a manual installation of imdisk) but without success. Besides, in some other occasion (loading the install.wim as source) I could see a "stop" red warning icon in the Source section and I do not know what is this warning for. I wonder if I'm missing something important... Thx in advance for your support mariella
  4. dual booting DOS and Win7

    Thanks Jaclaz. Actually, while reading the article I was so pernickety at the point I promptly saw the difference between the two strings NTLDR/BOOTMGR in the 2 cases. Thanks again for your clear explanations, though. mariella
  5. dual booting DOS and Win7

    Jaclaz, I meant that following the Win7 installation, an (already) existing FAT32 Boot Record results as being modified ! And this is pretty new for me. mariella
  6. dual booting DOS and Win7

    Thanks Jaclaz, I'll have a look at the MSFN thread you have indicated. Maybe, has this anything to do with what described in the following pages (still under construction) http://thestarman.pcministry.com/asm/mbr/ntFAT32BR.htm and http://thestarman.pcministry.com/asm/mbr/FAT32xp7comp.htm mariella
  7. dual booting DOS and Win7

    Jaclaz, OK. With the BOOTMGR process flow you attached you responded to my question. So that BOOTMGR looks for the \boot\BCD section, at first, and then it looks for the BOOT.INI part. The reason for my question was that on some thread/tutorial (I'm not able to remember any reference about it), I read that once the BOOT.INI file presence is confirmed, BOOTMGR skip to look for the BCD store section, directly taking into consideration only the entries in the BOOT.INI. Thx. mariella
  8. dual booting DOS and Win7

    @ Jaclaz, I'm trying to find the simplest way to have a FAT32 first partition (for installing MS-DOS -7.x or later), togheter with other NTFS primary partitions on an external USB HD. The method you indicated could be very interesting in my case, so I wonder if by using it I will end to have a real entry in the BOOTMGR choices (as you said) or, per default (and just due to its behaviour), normally the BOOTMGR loader will look for an active partition to start (through the created Boot.ini) and if it's not found it will look inside the BCD store. Thx, mariella
×