jaclaz

The "right" one should be this one: http://www.911cd.net/forums//index.php?showtopic=22716 On floppy it is possible that files go into root (instead of a subdir), see cdob's post in the above. jaclaz

Happy I contributed to make another happy bunny. http://www.msfn.org/board/cant-access-repa...27-page-10.html jaclaz

Can you elaborate on this? How were these files copied? The LOG is saying that you have 0 Mb source: jaclaz

@submix8 Unless I am mistaken, the OP posted: that he has a DELL XP ISO and the .iso ONLY jaclaz

No prob, we 8+3 max experts (dinosaurs) can read "between the letters" of a filename better than young people used to filenames (LUXURY! ) like: which of course means that you will create a lot of confusion once you will release other tools USB related. Since you are going anyway beyond the 8+3 go all the way : Completely unrelated, but sometimes colours are useful: http://en.wikipedia.org/wiki/Four_color_theorem If I may, I would re-add the feature of 0.9 (updating it of course) as an option. i.e.: Siginet's PLoP USB Boot Manager Installer + a radio button to EITHER: add PLoP only <-selected by default add PLoP AND grub4dos Though I do like "vertical" apps, a single choice is not overcomplicating it. Someone that wants to also have grub4dos would find your tool handy. jaclaz

Ahem... http://www.msfn.org/board/run-windows-7-xp...vt-t140245.html jaclaz

Most probably you have a SATA drive and miss the appropriate driver in the source. The dedicated forum to "Install Windows from USB" is casually named "Install Windows from USB" (as opposed to "Multi-Boot CD/DVDs") and is here: http://www.msfn.org/board/install-windows-usb-f157.html Check the FAQ's first thing: http://www.msfn.org/board/faqs-t116766.html If still it doesn't work (it would be very strange, as we have a great number of positive reports from the eeePC community) see if any of the alternate methods work. jaclaz

Actually we helped in WRITING the grub4dos guide : http://diddy.boot-land.net/grub4dos/files/thanks.htm If you are allright with it, I would split your post in a new thread dedicated to "USB seen as floppy" where we can continue experimenting, without increasing too much the length oc the "main" thread. I am afraid that you will need lot of patience as we will need to carry lots of experiments, but mo, we are not cornered (yet). jaclaz

I won't argue with you, either over this thing. If everyone is happy with calling this feature IFS, it's allright, I stand corrected, and everyone is happy. jaclaz

Well, no. (I mean yes ) If the chipset is supprted, PLoP gives USB 2.0 speed (MUCH faster) instead of BIOS USB 1.1 speed (MUCH slower) - of course this only applies to motherboards that have USB 2.0 capable chips and "dumb" USB 1.1. BIOS support. I am wondering if there is a misunderstanding. plpcfgbt works on plpbt.bin ONCE plpbt.bin is configured, you run plpgenbtldr.exe in order to create the loader plpbtldr.bin for plpbt.bin jaclaz

Workarounds: http://www.sevenforums.com/system-security...inistrator.html http://www.howtogeek.com/howto/windows-vis...-windows-vista/ http://www.recipester.org/Recipe:Add_%22Ru...dows_7_37738078 It should be possible to also add the command to the "default" action for the file type, i.e. the one that is executed by double clicking. jaclaz

No, it's not! IFS in DOS are implemented as device drivers or use the network redirector. Yes, it is. A device driver as an executable is really a device driver, MSCDEX.EXE "drives" the "unknown" hardware (the CD-ROM device), not only the filesystem. You could have taken a better example, like NTFS4DOS to prove your theory. But I won't argue with you on definitions. http://en.wikipedia.org/wiki/Installable_File_System JFYI: http://www.pcausa.com/resources/ifsqlist.html#AnchorCPhantom http://decuslib.com/decus/vmslt99a/nt/ http://groups.google.com/group/comp.os.msd...f208bd4668f2090 http://coding.derkeiler.com/Archive/Assemb...7/msg00198.html jaclaz

Just a semi-random idea, but it seems like that camera: http://www.camera-warehouse.com.au/p/nikon-d5000 has MPT. For MPT: http://en.wikipedia.org/wiki/Media_Transfer_Protocol a package from MS does exist: http://www.microsoft.com/downloads/details...;displaylang=en which is said to work on 2k also. http://msdn.microsoft.com/en-us/windows/bb190309.aspx http://www.i-freeware-download.com/info/Me...-ifpd-9959.aspx of course your mileage may (and will) vary. jaclaz

Yes, there is a GREAT difference between "el-cheapo" "no-name" and "top level" sticks, often there is a 4x or 5x speed factor in comparative tests. Yes. The problem is not the massive read access (no or very little wear derives from it). Nor the write of huge chunks of data (as it will take time and it counts anyway as a single write operation). So, with FAT16 or 32 or EXT2FS it isn't likely that there will problems soon , unless you defrag constantly a filled up to the brim filesystem. NTFS or EXT3FS do at least one write operation for each READ one, that and as well the activity of a swap file can wear a stick in weeks of use, if it has not wear leveling capabilities. The Optima-Pro should be a PNY, that I think uses a UT165 from USBest, which actually HAS wear leveling: http://www.forensicfocus.com/index.php?nam...sc&start=34 A wear leveling algorithm, depending on several factors, like the amount of "fill" the filesystem is at, can easily introduce a x10 to x30 factor in life of the device, but it also greatly depends on the type of wear leveling algorithm (static vs. dynamic). A couple of resources with some actual figures: http://blog.datalight.com/flash-wear-leveling http://www.flashmemorysummit.com/English/C...1_F2B_Roman.pdf AFAIK, the whole idea of a IFS (Installable File System) is post-DOS. In DOS the filesystem needs to be inside the kernel. There are LTOOLS, though: http://www2.hs-esslingen.de/~zimmerma/software/ltools.html jaclaz

plpbt.bin CANNOT be loaded by NTLDR/BOOT.INI. That's why the plpgenbtldr.exe (please read as PLoP generator of NTLDR compatible loader) was made. The program creates a plpbtldr.bin on the specific machine able to "connect" NTLDR to plpbt.bin. In other words: NTLDR->BOOT.INI->plpbt.bin is NOT possible NTLDR->BOOT.INI->plpbtldr.bin>plpbt.bin is Are you sure you followed exactly the instructions I quoted from the PLoP site on the other thread? http://www.msfn.org/board/launch-usb-setup...ws-t140388.html Whay don't you post on the PLoP forum reporting the issue, once you have double checked everything? jaclaz

Meadow double posted, here is the rest of the story: http://www.msfn.org/board/have-gone-wrong-t140439.html jaclaz

Does Dell produce the eeePC (901 or other model)? @Meadow The problem is your source. It is NOT a "good" Windows XP CD, is a "crapified" DELL OEM one. Besides the fact that it is an infringement of the Eula to use such an OEM OS on another machine, why do you think that this app has been created?: http://www.pcdecrapifier.com/ Get a valid XP source CD. jaclaz

That's the important thing, to have a plan, but time and patrience will be needed too : You are welcome. Being around 9 PM here right now, I'll have a great night instead, if you don't mind jaclaz

PHOTOREC: http://www.cgsecurity.org/wiki/PhotoRec If you know the file types it should be also rather quick. Or any other file recovery software. See also here: http://www.msfn.org/board/recovering-accid...es-t113511.html http://www.msfn.org/board/data-recovery-tool-t84345.html jaclaz

Most probably - for this "vertical" use - you can configure plpbt.bin: http://www.plop.at/en/bootmanager.html#plpcfgbt jaclaz

I am not sure to understand the question. Do you want to install a .inf file from command line or a batch? The usual way is using RUN32DLL.EXE with either advpack.dll or syssetup.dll http://www.msfn.org/board/can-install-inf-...ne-t104891.html jaclaz

Yes, I suggested grub4dos as it allows more "flexibility" and future additions. Yes , this would be - by chainloading directly plpbtldr.bin from BOOT.INI - the very minimal and non-intrusive solution for single OS booters on a non-USB enabled at boot-time motherboard. Please also note that in several cases whilst the actual chips in the motherboard are USB 2.0 compatible, the BIOS only loads at boot time at 1.1 speed, in these cases using PLoP even if the motherborad supports USB booting gives a very noticeably speed boost to the process. jaclaz

Actually, what I suggested was rather the opposite. Leave device manager alone. Close windows/switch the PC off. Disconnect the old mouse. Connect the new mouse. Switch PC on. Let XP do whatever it thinks fit detecting the new device. As said most probably the mouse will work allright. Then you update the driver. Any USB device has a VID (Vendor ID) and a PID (product ID) but they also belong to a given "class", which is the same for all USB mice. It is possible that the previous "specific" Micro Innovations driver did not "like" the Logitech VID/PID, though it's strange. If the above does not work with the MS mouse too, the alternative is: Open device manager. Remove the mouse device (don't worry you won't lose instantly mouse control) Close windows/switch the PC off. Disconnect the old mouse. Connect the new mouse. Switch PC on. Let XP do whatever it thinks fit detecting the new device. As said most probably the mouse will work allright. Then you update the driver. jaclaz

You shouldn't have any problem. The XP should recognize the new device as mouse and either use the old driver (if compatible) or use the "default" one, both should allow "basic" mouse working (maybe some fine-tuning settings won't be available), as well as additional buttons and in some cases the mouse wheel, but moving the mouse and left and right clicking should work allright. Then you can install the "new" specialistic driver for your new mouse. jaclaz

If I may, there are simple apps, nonetheless WYSIWYG, as an example this one, which besides being Freeware/Open Source, is also connected to the W3C, i.e. the people that actually try to set standards on Web design: http://www.w3.org/Amaya/Overview.html This one is nice too: http://www.kompozer.net/ You can do a page in Word or Frontpage allright, as long as you later trim it down removing all (or most of) the bloat, there are programs for this: http://www.w3.org/People/Raggett/tidy/ http://tidy.sourceforge.net/ Validating the html is also a good idea: http://www.w3.org/QA/Tools/ Also testing it in different browsers is advised, besides local testing, there are web resources, an example one: http://browsershots.org/ jaclaz