Jump to content
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. ×


  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

0 Neutral

About seahorser

Profile Information

  • OS
    XP Pro x86
  1. winnt32.exe /unattend:[file produced by nlite, which shows partition selection in text mode setup when run from usb] and selecting the directory which will windows will install later etc. options from winnt32 wizard ends-up with the usual folders $WIN_NT$.~LS and $WIN_NT$.~BT. Then I modify the \$WIN_NT$.~BT\winnt.sif to include the [Unattended] and other sections which winnt32 removes from my original winnt.sif. I have Autopartition="0" flag at all times in [data] section. When the computer begin the text mode phase, it continue to install windows in C drive without to show any question
  2. I didn't say otherwise! It was revert to UP. BIOS reported one processor on any clean XP 2003 etc. installation I was trying, so both Device Manager and Task Manager shows what they think they find. Also I was try to force install the MP HAL (also try all the other options it has that menu) using F5 key on a new XP setup, but again windows shows one core. The problem solved by reloading the BIOS default settings (although the settings are the same). PS. Some years ago I was see the following peculiar problem: The PC doesn't POST and doesn't boot. Believing that the GPU had fail (from
  3. If it is exists and it isn't something else, like BIOS rootkit which control the other core individually from the OS by side channel, it must be hidden. There isn't any setting like this anywhere in the BIOS tabs. I can take pictures of the BIOS if you don't believe me.
  4. Problem solved by reload default BIOS settings (F9 in this m/b) and suddenly 2 processors appear in device manager. The previous BIOS settings and the "new" reloaded defaults are the same as I double check them before and after!!! Another mysterious aspect is that before the reload to defaults action, I had try to change the NoExecute memory protection and the Enhanced Halt State to Enable but then the XP stays forever in a blank screen so I have to press the hardware reset button. XP detect the reset and they boot to safe mode just fine, but then they won't boot to normal mode as long as BI
  5. Msconfig shows one CPU and the numproc value isn't in use (none of the options is in use). In fact I never use Msconfig. Occasionally I use autoruns. Also the new test installations I was saying in my first post didn't have any chance to run msconfig. This motherboard BIOS doesn't have the OS compatibility setting which had earlier motherboards. What you mean by reset the BIOS? Load default values or re-flash it again with the same BIOS version? If is that the case, that should mean that a very sophisticate BIOS level firmware is sitting there...
  6. Device manager shows one processor. The CPU is Core 2 Duo. I don't think my BIOS has the ability to disable cores. BIOS has: Enhanced Halt State, Intel virtualization tech, CPU thermal throttling, Intel speedstep tech, No execute memory protection, Intel C-STATE options. I have try some combinations with enable and disable settings but windows still shows one processor on the Device Manager, whatever the Computer is ACPI multiprocessor PC or ACPI uniprocessor PC.
  7. On the performance tab I remember that I see how many cores a CPU had by separate "CPU Usage History" columns (one graph for each core). Also on the View menu there is an item called "CPU History"->One Graph Per CPU. My old XP and any new installations I make for that matter, even with different Hardware Abstraction Layer than ACPI (by pressing the F5 key early at text mode setup), all show one graph at CPU Usage History where my CPU isn't a single core CPU. How I get Task Manager like this ? PS. I feel that I'm going loose on my memory :(
  8. From my first post all this time I experience sudden lockups, freezes and reboots. Several times windows setup tell that "some xxxx line in txtsetup.sif is invalid", grub4dos dies after recognize usb etc. The same UFD with exactly the same files, sometimes boots to windows setup and others freeze etc on this old BIOS. When I remove some stuff using nlite it may go to the famous 7b error, but it never arrive to the screen which shows disk/partitions to choose for the installation to continue. It is not a hard disk controller driver issue either because the disk is IDE. To investigate furth
  9. I don't know at which UFD format scheme you refer to. My current UFD format is made from fbinst from within WinSetupFromUSB 1.9 using as format options chs zip force and import the grldr to the primary data area and also copied to the root of the UFD. I boot straight to grub4dos without any menus or scripts. Find command give me a list of: (ud) (fd0) (fd0,0) (hd0,0) (hd0,1) (hd0,2) (hd0,3) , map ( and TAB give me fd0 hd0 rd ud. geometry (fd0): drive 0x00(CHS): C/H/S=370/255/63, Sector Count/Size=5944050/512 partition num: 0, active, Filesystem type is fat32, partition type 0x0C Fi
  10. Didn't try because the main script winsetup.lst needs RDSK variable. I set RDSK=1 in shfthd.bat as I already know that by usb --init one more device (the hd1) appears to grub4dos. The whole setup procedure from start to finish after my modifications to the shifthd.bat runs fine on the newer PC but on old BIOS (AOPEN AK86-L) it freezes when windows setup loads kernel debugger dll. I also try several e820cycles values within winsetup.lst and some grub4dos versions with fbinst without any success. I try all and some of your commands and I get hd2 (0x82) when execute usb --init, so I didn't p
  11. My BIOS doesn't have USB-HDD option and I can't able to to boot with USB-FDD option. Only USB-ZIP is working. drive 0x80(LBA): C/H/S 38913/255/63, sector count / size 625137345 / 512 partition num: 0, active, NTFS, 0x07 partition num: 1, NTFS, 0x07 partition num: 2, NTFS, 0x07 partition num: 3, FAT32, 0x0C When I use BOOTICE's UltraISO v2+ using boot code USB-ZIP+ v2, "hide boot part" to hidden with boot partition size 32MB FAT16 Grub4Dos (grldr), "Data partition" FAT32 with size the rest of space I get: drive 0x00(CHS): C/H/S 30020/64/63 sector count / size 1210378
  12. At best all I can get are a bunch of registers and by hitting any key the screen displays several more pages of them. Then it hangs. What I have to do with those DX,BP,AX etc. registers? I try to follow that approach but I'm stuck in mud. I barely understand 30% of what they say. That is not step-by-step walk-though. He jump to conclusions without to present us how he got there. What commands gave to debug (I assume that he got boot from the internal hard disk to DOS then run debug.exe). How I can get the values for LLLL and SSSS?
  13. That BIOS you describe is very "queer". M/B is AOPEN AK86-L Grub4dos (before usb --init) sees 4 FDD partitions (fd0,0) (fd0,1) etc. That thread is huge although I'll try it. 1): I had wrote in my first post I use version 1.9 2): I just try the 1.0 version. At fbinst I reformat the UFD by using chs + zip + force options then I drag-drop grldr 0.4.6a. Test it to see if it boot to grub4dos and is OK. Then I continue with "Add to USB disk" and the two advanced options mention earlier. The results are exactly the same. The script tries to shift the drive a
  14. My old BIOS has only USB-ZIP and USB-FDD and support USB2.0. It only boot from USB when my UFD is formatted with 2 partitions. The first one had to be FAT16 32MB hidden, and the second FAT32. I create successfully and boot those partitions either through BOOTICE using the U+V2 button, with dummy.sys driver and with WinSetupFromUSB v1.9 FBinstTool. I try to install XP from USB to the internal IDE disk which I know is recognized by WinXP SP3 official ISO disk, so I select the 1st option and check the "Don't check for and install grub4dos MBR" and "Do not copy and use DPMS" at the advanced o
  15. When installing from C: which is a DOS FAT32 partition on the drive, the XP setup ends up to the D: drive letter as expected which is NTFS partition. How I get the C: drive letter (SystemDrive) on Windows XP which begin to install into the second partition (or into 3rd partition etc.)? Is it possible for the XP setup to use the C: drive letter when was used initially by the setup at any other stages like T-whatever? I want to have Windows in C: where the C is assigned to second partition (or 3rd etc.).
  • Create New...