jaclaz

Or half-way, maybe? jaclaz

I don' t know if it is the same thing, but once we had the board autocorrect (replacing some characters with asterisks) words like Fukushima (no workaround possible) and Matsushita (we had to write Panasonic to get through the word filters ) Welcome aboard! jaclaz

Sure . requisites for using an F6 floppy are: 1) a floppy drive 2) an actually suitable F6 floppy media requisites for grub4dos floppyless F6 are: 1) grub4dos 2) an actually suitable F6 floppy media image If you miss #2 both methods become complex. jaclaz P.S. Before I forget, a similar approach using Syslinux: http://wp.xin.at/archives/2702

0xc0000142 means missing (or unregistered) .dll Usually tracing the .exe with Dependency Walker the culprit can be found. jaclaz

That is probably fine since there is NO image in my post. There is instead a preview - auto-generated by the stupid board software - of a youtube video, link is: https://www.youtube.com/watch?v=3mbd9qEzU5Q jaclaz

Well, yes and no. It supposes that you have a network and one of the machines is running a recent OS and has internet connection. Unlike a virtual machine, this is simply a "proxy", but it allows connecting your "real" machine running an old OS to the modern Internet. jaclaz

You mean something *like*: jaclaz

Basically, AFAICU you are replacing (forcing) the driver to a not-the-right PCI/VEN. IF - for whatever reasons - the new driver doesn't start AND the old IDE driver does not (on reboot with the BIOS back to IDE) still work you are left with a non-bootable system. Of course recovery of such a system is always possible, think of the good ol' mergeIDE, but it is not like it is (anymore) common knowledge: (currently the above link resolves to ANOTHER MS KB page, use an archived version to get the mergeide.reg: https://web.archive.org/web/20100723171255/http://support.microsoft.com/kb/314082/ And you need to somehow boot the computer with a PE (or have another OS or another computer) to use that. jaclaz

@Luweitest I cannot think of anything more risky than what you reported doing, however, if it worked for you, good. Still it is not the "right way", which is the one already posted by me and cdob (i.e. have the driver be "parallel" to the IDE one), allowing, in case of issues with the new driver to re-set the BIOS to IDE and have the previous driver (almost) surely working. It is very possible that XP has some "safety mechanism" that allows anyway to revert to the IDE driver if the SATA one fails and you re-set the BIOS to IDE, but it remains IMHO risky, if one makes before an integral copy of the disk, then it may be attempted, but otherwise ... jaclaz

Sure you can, that is the whole point of the first links I gave you and of the one cdob provided . jaclaz

Well, the RMPREPUSB tutorial actually loads two (or more) drivers, in that case it is a single SATA driver + Firadisk (or Winvblock), but you can replicate the same with the two drivers you have: http://rmprepusb.blogspot.com/2013/06/txtsetupoem-files-for-f6-floppy-disks.html AND check how the TXSETUP.OEM in the floppy Steve6375 provides is made: https://www.rmprepusb.com/tutorials/install-xp-from-an-iso/winvblockJmicron_C600.ima.gz.gz?attredirects=0 But also the manual you posted seemingly uses the "Press S to add driver" approach, maybe the issue is specific to the "Marvell shared library (install first)" ? jaclaz

Conventionally the "pipe" sign "|" means "or", these (from JFX's post) are valid options: BootMountExclude=\Device\HarddiskVolume1 OR BootMountExclude=Disk0 OR BootMountExclude=Disk1 jaclaz

Maybe useful, maybe not, just found this : https://github.com/tenox7/wrp jaclaz

No, the mapping is "volatile". But there should be not AFAICR the need of a reboot, or - better said - after the reboot text mode-> GUI setup there should be no need of the floppy. What happens (or should happen) when you press F6 and choose the files is that the files on the floppy are copied from the floppy to the C:\$WIN_NT$.~BT folder Maybe there are still some issues with the floppy contents and/or oemsetup.txt? To verify that a file in contiguous in grub4dos you simply run the command "blocklist", i.e.: blocklist /floppy.img the result will be something *like* 322158+2880 (which means that the file starts at LBA 322158 and extends by 2880 sectors, and the file is contiguous, if it is not you will have more that one result in the form start+length, one for each extents of the (fragmented) file. Being contiguous is a requisite if you do "plain" mapping, i.e.: map /floppy.img (fd0) while it is not needed if you do a memory mapping, i.e.: map --mem /floppy.img (fd0) Review this tutorial/approach: https://www.rmprepusb.com/tutorials/install-xp-from-an-iso and this one (about the F6 floppy): http://rmprepusb.blogspot.com/2013/06/txtsetupoem-files-for-f6-floppy-disks.html In that method - if I recall correctly - the Winvblock (or Firadisk) driver is used only to keep the .iso accessible during the GUI part of the setup, and the floppy is not re-accessed after the reboot, from what you report it looks like some file is not found and the GUI asks for the floppy. If you cannot find the reason why, you can still prepare a USB stick with Winntsetup from USB or follow the RMPREPUSB tutorial above. jaclaz

If you want/can start DOS (Win 9x DOS is fine), you just: 1) put in a reachable path grub.exe and the floppy image you want to map 2) execute it 3) at the grub4dos command prompt run the needed commands (or have a menu.lst with them) 4) boot to *whatever* you want to boot to start the XP installation Example, imaging that you boot to the C:\ drive and you have in it C:\grub.exe and C:\myF6floppy.ima At the dos prompt: grub.exe [ENTER] at the grub prompt: find --set-root /myF6floppy.ima [ENTER] map --mem /myF6floppy.ima (fd0) [ENTER] map --hook [ENTER] chainloader /io.sys [ENTER] boot [ENTER] Back to Dos prompt: DIR A:\ [ENTER] should list contents of the F6floppy The guide here is old (but good enough for this use): http://diddy.boot-land.net/grub4dos/Grub4dos.htm Starting XP installation from DOS (i.e. via WINNT.EXE) you are limited to FAT filesystem, of course, though you can later convert it to NTFS. You can use either an oldish, stable grub4dos 0.4.5c: http://grub4dos.chenall.net/downloads/grub4dos-0.4.5c-2016-01-18/ or a recent grub4dos 0.4.6a: http://grub4dos.chenall.net/downloads/grub4dos-0.4.6a-2019-06-17/ (later versions may do as well, but since they are experimental you'd better stick to older ones). In some cases (it really depends on moptherbards) you may need to map the floppy also to (fd1) besides (fd0). jaclaz

Yep , the 4.60 vs. 4.71.2 is another issue that is long-standing (and that originated the ForceASPI set of sctipts), AFAICR it depends a lot on the combo of OS/Motherboard/SCSI card AND software in use. I will confess that I do have *somewhere* an oooold SCSI Plextor CD drive (one of the earliest models, 1x or 2x, that use a caddy/cartridge for the CD) on a NT 4.00 machine with an Adaptec SCSI 29xx card which I use - maybe once every year or every two years - to recover contents of CD's that more modern drives simply cannot read and that particular setup - if I recall correctly - uses ASPI 4.60, though I rarely use it for music CD's/with EAC. Anyway modern releases of EAC should need not an ASPI layer and use SPTI, though actual behaviour needs to be tested on the spoecific machine/setup. Keep us informed on the results of the test with the Starburn drivers ... jaclaz

No (AFAICT/AFAICR). You need to use grub4dos (or similar) that maps the image to a floppy at BIOS level. I don't understand, however, you have a problem, for which a solution has been already been found (and tested/verified), why not trying it before speculating on alternatives? IF what was suggested (which - I repeat - has been already tested and verified by hundreds or thousands of users) doesn't work in your case THEN it will be time to look for alternatives. If you ned assistance/help to implement the grub4dos loppy mapping, just ask. jaclaz

ASPI has been historically not supported by MS (and delegated to Adaptec) and SPTI was used: https://web.archive.org/web/20140203072159/http://support.microsoft.com/kb/182542/en-us Adaptec is no more, and a quick search on the site www.adaptec.com resolves to: https://www.microsemi.com/ which gives no results for ASPI, but something can be found on https://storage.microsemi.com/ https://storage.microsemi.com/en-us/speed/software_pc/aspi/aspi_471a2_exe.php (I believe it is the latest ASPI version from Adaptec ) So, it is years that the FrogASPI exists, it is a mapping of ASPI commands to SPTI ones, at least on 32 bit systems it worked just fine, but in your case I would try to use the Starburn drivers (that have been tested on Windows 10 x64, at least in a VM, with success), see: http://wp.xin.at/archives/829 jaclaz

Not really . On its page on tetris wiki (which I referred earlier for possible alternatives): https://tetris.wiki/Tetris_(Microsoft_Entertainment_Pack_for_Windows) More info and some screenshots here: http://www.thealmightyguru.com/Wiki/index.php?title=Tetris_(Windows) Interestingly enough, it seemingly bears the logo of "Bogus Software": https://web.archive.org/web/20110415064416/http://www.download-central.ws:80/Win16/Tetris/Windows/ And it is seemingly also known as Wintris: https://everything2.com/title/Wintris but licensing/sub-licensing apart the game is definitely written by Dave Edson: https://books.google.it/books?id=O5j5DAAAQBAJ&pg=PT62&lpg=PT62&dq=tetris+"dave+edson"+microsoft&source=bl&ots=MWD8s938S6&sig=ACfU3U1R63e9xC48wsQdNw_vsmefmzz0yg&hl=it&sa=X&ved=2ahUKEwiSg6Gw2rnjAhUEyqQKHXBmA6oQ6AEwDXoECAkQAQ#v=onepage&q=tetris "dave edson" microsoft&f=false http://www.kraigbrockschmidt.com/mystic-microsoft-05/ https://www.linkedin.com/in/dave-edson-89991620/ jaclaz

The best way to use a F6 floppy (without a floppy drive) is using grub4dos to mount it (its image) virtually, this is what I suggest you for the next boards: or even easier, use winsetupfromUSB: Since you have the XP already installed, yes, you can change its mode, it is not easy, not for the faint of heartm byt you surely can do it with a bit of patience: http://forums.pcper.com/showthread.php?444831-HOWTO-enable-AHCI-mode-after-installing-Windows jaclaz

Ok, the easiest is - strangely enough - the most complex one If you have an USB stick available, the best option is making it boot a grub4dos, then add *any* Win9x/ME floppy image and boot to it. Can you make the USB boot FreeDOS? Or what OS are you running "normally"? If *any* Windows NT, use (it is the easiest) RMPREPUSB: https://www.rmprepusb.com/tutorials/grub4dos#TOC-Part-1---Making-a-bootable-USB-pen- Then you can boot the floppy image *like*; http://diddy.boot-land.net/grub4dos/files/map.htm#image jaclaz P.S.: there has been in the past a mess with FreeDOS SYS, maybe you have the "wrong" version, see here: http://reboot.pro/topic/15123-freedos-bootsectors/ or try getting the actual one here: http://www.fdos.org/kernel/sys/

A .reg file is a simple .txt file, you can open it in - say - Notepad just fine. All changes go to: The Disable Shim adds values *like*: The Enable Shim deletes the same values *like*: See: http://www.zeda.nl/index.php/en/remove-keys-using-reg-files jaclaz

To be picky (as I am BTW) the FreeDOS MBR expects - just like the DOS one - an active partition, whilst the FreeDOS PBR (or bootsector) of the active partition will expect the KERNEL,SYS instead of the IO.SYS BUT you can still use the FreeDOS SYS command with the /OEM:W9x switch, http://help.fdos.org/en/hhstndrd/base/sys.htm jaclaz

I don't know, personally I can accept just fine the notion that the good MS guys are (again, not everywhere but in spots) a bunch of evil bastards. jaclaz

Stuffing keyboard buffer? jaclaz