jaclaz

What the HECK is the actual question(s)? This Forum: MSFN Forum> Microsoft Software Products> Windows 95/98/98SE/ME> Windows 9x Member Projects http://www.msfn.org/board/forum/91-windows-9x-member-projects/ Corresponds loosely to this one: MSFN Forum > Member Contributed Projects http://www.msfn.org/board/forum/102-member-contributed-projects/ It has been moved to inside the Windows 95/98/98SE/ME as it is of limited popularity and practically used by a small number of aficionados - And normally NO, you CANNOT use 9x files on XP, but you may want to try using NT 4.00 or 2K ones, example: but I don't think that any "old version" will solve any of your "problems". At first glance, it seems to me that most of your problems derive from using Explorer, either as shell or as filemanager. What was the sense of double posting? jaclaz

I see that you are pessimist (just like most people behind the green glass door) but countless and innumearable blessed buddies over there only see the half full glass. jaclaz

Yep, you are definitely confused. Windows 9x/Me is currently compatible ONLY with FAT12/FAT16/FAT32, though there are tools to access (NOT boot from) NTFS. Windows NT 3.5 and 4.0 only have FAT12/FAT16 and NTFS (and early version) thoutgh there are tools to access (NOT boot from) FAT32. WIndows 2K and later support natively FAT12/FAT16/FAT32 AND NTFS. Transfer speed of a USB device depends on FOUR things: actual BUS speed (hardware of the PC) actual device speed (hardware of the USB stick, NOT all sticks are the same) actual driver speed (depending on OS) actual size of files (several smallish files are slower than few bigger ones) The filesystem used in my experience is actually not as relevant as the above, compare: If you want to boot from the USB stick, RMPREPUSB is recommended, but you can choose among several ones, listed here: http://reboot.pro/9460/ jaclaz

Yes, as said you are missing some basics. The actual MBR (Master Boot Record) in the "usual" form of the MS operating systems (i.e. NOT a multiboot MBR). Has FIVE main functions: hold the partition table data (four entries, each 16 bytes long) that represent addresses of the partitions hold the disk signature (four bytes) on NT/2K and later systems ONLY find which of the four entries has an active state (i.e. check that either byte 0x01BE, 0x01CE, 0x01DE, 0x01EE is 0x80) check optionally that the actual partition entry marked as "active" as per above is NOT "hidden" (i.e. that it's partition type does NOT begin with 1 or 2) (some MBR code versions will not work with hidden active partitions) http://www.win.tue.nl/~aeb/partitions/partition_types-1.html call the bootsector of the partition or volume makrked as active Since it is called "Master" even semantically it implies that some "Slave" boot record must exist. If you use a boot-loader, like grub4dos, you can "by-pass" BOTH the MBR and partition bootrecord and directly load the OS kernel, an example for DOS 7.x/8.x (a.k.a. Windows 9x/Me), create a bootable floppy running grub4dos then, you can boot your DOS/Win9x on first partition of first hard disk INDIFFERENTLY with: chainloader (hd0)+1 the above chainloads the MBR (which chainloads the PBR, which chainloads the kernel) root (hd0,0) chainloader +1 the above chainloads the PBR or bootsector (which chainloads the kernel) root (hd0,0) chainloader /io.sys the above directly chainloads the kernel file BUT you need anyway some data in the MBR (the partition table data) and in the PBR ( the BPB or Bios Parameter Block), and of course the "magic bytes" 55AA. These are detailed in the given links. But you can try creating a FAT32 filesystem with apps like the FAT32 Formatter: http://reboot.pro/2959/page__st__7 and you will see at a glance which parts are needed in the bootsector to actually boot. jaclaz

if %found% == 1 ( and you have some "queer" spaces, that may prevent the actual working. but there should be simpler ways, here is one: @ECHO OFF SetLocal EnableDelayedExpansion IF EXIST alive.txt del alive.txt IF EXIST nosysaid.txt del nosysaid.txt FOR /f %%q in (win-segment.txt) DO ( FOR /f %%r in ('TYPE blacklist.txt^|FIND "%%q"') DO ( ping %%q -n 1 -w 20 if !errorlevel! equ 0 echo %%q >> alive.txt pause ) ) and here another one: @ECHO OFF IF EXIST alive.txt del alive.txt IF EXIST nosysaid.txt del nosysaid.txt FOR /f %%q in (win-segment.txt) DO FIND "%%q" blacklist.txt 1>nul&&ping %%q -n 1 -w 20&&ECHO %%q>> alive.txt jaclaz

You seem like thinking that behind the green glass door there is a police state , (which is not ). The greengrocer was actually necessitated and beseeched, and all happened in an unconditionally affectionate, compassionate and chummy manner. He admitted, but happily, and confessed, but effervescently, what he would have otherwise freely and on his own accord communicated. jaclaz

You really need to take some time to READ the given links. It's called "bootsector" do you think that it's code will be executed when booting? jaclaz

Yep, the greengrocers behind the green glass have plenty assortment of alluring and queer berries, but miss many basic vegetables, like no peas nor usual beans, they do have pellets, nuggets and seeds, though. Bestsellers afaik are runner beans and green beans. Common are also bitterleaves, broccoli and brussels sprouts, radicchio, lettuce and swiss chards aplenty, beet greens but no spinaches. Chinese cabbage and Fiddleheads, but no artichokes, nor potatoes. jaclaz

Basically we DO NOT have a tested procedure. The 5400.6's DO NOT suffer from the SAME problem as the 7200.11 do, so, even if the symptoms are the same it is likely that the cause is different. If you had spent 5 (five) minutes to search the board you would have found this: and this: jaclaz

It is perfectly possible that there is a "robots.txt" preventing indexing a part of the forum and not another. http://en.wikipedia.org/wiki/Robots_exclusion_standard You should ask the actual Forum Administrators if such a policy is in effect and how it is set. jaclaz

What is the difficult part in the README first? READ ATTENTIVELY point #10! Draw your own conclusions. jaclaz

The MBR is NOT the bootsector. This is where you probably are confusing matters. Normally the bootsector of first partition is at sector 63 (CHS 0/1/1) on "legacy" systems (up to XP/2003) and on sector 2048 (CHS 0/32/33) on Vista :ph34r:/2008/7 (if not patched to follow "legacy" Rules) The MBR is NOT part of the volume, it is part of the disk. Review this: http://mirror.href.com/thestarman/asm/mbr/DiskTerms.htm http://mirror.href.com/thestarman/asm/mbr/DiskTerms.htm#LOC and take some time on the Starman's pages to understand the structure of disks and partitions and volumes and filesystems. First sector of a hard disk (sector LBA0) is the MBR or Master boot record. The bootsector of a partition starts at first sector of the partition or volume, as said for first partition it is normally LBA 63 or 2048 depending on the OS that partitioned the volume. More generally you read the partition table in the MBR (and for extended partitions in the EPBR chain) to know where the bootsector of a given partition starts. FAT 12/16 the bootsector is 1 sector long FAT32 the bootsector is actually 3 sectors long, first, second and third if formatted under DOS/Win9x/Me: http://mirror.href.com/thestarman/asm/mbr/MSWIN41.htm first, second, third and thirteenth: http://mirror.href.com/thestarman/asm/mbr/FAT32brcomp.htm if formatted under 2K/XP and later (for the record, for unknown reasons the FAT32 of ReactOS uses 15th sector innstead of 13th) jaclaz

NO. Look, it works this way, in the Registry *something* says to start the intelppm driver (and - as said - the other ones mentioned) automatically. If you delete the file the *something* will try to start it nonetheless. You need to disable the *something*, i.e. set it so that it only starts "on demand": You can check if the "old" motherboard install the HAL uses a "normal" ACPI Uniprocessor HAL that will also support a multi-processor motherboard (Halaacpi.dll) http://support.microsoft.com/kb/309283/en-us Another option is offline sysprep: http://www.911cd.net/forums//index.php?showforum=43 jaclaz

Well, the easiest would be HDhacker but is NT/2k and following only. Beeblebrox and similar tools tend to just save the first sector (which actually in the case of FAT32 is however the only one containing meaningful DATA). For DOS you can use MBRwizard http://mbrwizard.com/ you want the "Legacy" version, please note how you need to get to the firesage site through the above "old" site in order to get the "Legacy" tab. But more generally any disk editor working under DOS/Win9x will do, a good one is the PTS-DE one: http://mirror.href.com/thestarman/tool/FreeTools.html#PTSDE http://mirror.href.com/thestarman/tool/de/PTS-DE.htm jaclaz

It's actually this one: http://www.theabsolute.net/sware/dskinv.html It is not - as a general rule - a good ide to link to a .exe file directly. It is clearly a gltch of the program. Open the disk in any "simple" tool, like the ones listed here: http://mirror.href.com/thestarman/asm/mbr/BootToolsRefs.htm or beeblebrox: http://replay.waybackmachine.org/20080423005903/http://students.cs.byu.edu/~codyb/ http://replay.waybackmachine.org/20060223003038/http://students.cs.byu.edu/~codyb/beeblebrox9xsetup.zip You will see that these data: Total logical sectors: 1062876402 Cylinders: 625 Sectors per cylinder: 63 Heads: 255 will remain the same (they are physical values of the actual hard disk). However, I was incorrect, these data come from system calls, particularly the 129 means drive 0x81 i.e. second drive in DOS (as taken from the BIOS) and the rest are physical values, but the cylinder one is also blatantly wrong. 625*255*63=10,040,625 sectors * 512=5,140,800,000 so they make NO sense. On the other hand, the value of 1,062,876,402+63=1,062,876,465/63=16,871,055/255=66,161 Cylinders Your disk should have a "virtual CHS geometry" of 66,161 or 66,162/255/63 jaclaz

Are you refeering to the two .txt files? WHAT did you use to make them? Anyway these: Are info that come from the MBR (and not from the bootsector) i.e. from PhysicalDrive and not from LogicalDrive. jaclaz

More specific info: http://mirror.href.com/thestarman/asm/mbr/MSWIN41.htm http://mirror.href.com/thestarman/asm/mbr/MSWIN41.htm#FSINFO Definitely byte 0x30 should be 0x01. What is not clear (to me at least) is whether this provision was "born" with FAT32 or it was added *sometime* later. jaclaz

Actually the issue is with the TOTAL length of the power leads : basically it's the TOTAL length from the power supply to that actual board that may (in some particular cases and ONLY with "bad" power supplies that send the spikes) create a voltage peak when switched on (capacitor effect). This SHOULD NEVER happen (i.e. no way it can happen ) if you power the PC BEFORE and later connect the Molex. There is NO possible switch bounce WITHOUT a switch (unless of course you have delirium tremens ) It WON'T happen if you use a battery to power the adapter. You may want to do it behind the green glass door where there are NO switch bounce nor voltage peaks, and lots of TTL-converters...(but NO USB ) The USB to TTL seems to me the best choice of the three mentioned as it is ALREADY powered by the USB BUS and you need not to fiddle with the power supply, you just insert the device in a USB port. jaclaz

Yes, usboot approach may work. The alternative being following the "good ol'" method by Dietmar (tutorials are in his signature): http://www.911cd.net/forums//index.php?showtopic=14181 you want to use Tutorial 3: http://www.911cd.net/forums//index.php?showtopic=14181&st=228 and/or Tutorial 6: http://www.911cd.net/forums//index.php?showtopic=14181&st=1515 with the added feature of USbbootwatcher: http://www.911cd.net/forums//index.php?showtopic=22473&hl= But yes, your mileage may vary. jaclaz

Well, with all due respect , if you got it from pololu how come you didn't read the NOTE: it's quite visible. WHERE are you based? India? Get this: http://www.embeddedmarket.com/products/USB-to-TTL-Converter-Module/ (just an example) Another one: http://www.rhydolabz.com/index.php?main_page=product_info&products_id=302 An USB to TTL one: http://www.rhydolabz.com/index.php?main_page=product_info&products_id=304 jaclaz

Yes, unfortunately it MAY happen. It is a RARE condition, but it may happen with a re-start (as opposed to switch off) in certain conditions. Compare with the issue detailed here: http://www.pololu.com/catalog/product/126 http://www.pololu.com/docs/0J16/all jaclaz

No elevenses but abbundant prenoon booze intermissions or recesses and they also indulge mollycoddle in the habit groove of Yukkaflux http://bigblogofbooze.blogspot.com/2005/12/dictionary.html BTW, they have no oranges, but apples a lot and plenty berries, expecially Abyssinian Gooseberries and Yellowberries.... jaclaz

Rule of thumb has always been to use the SAME SP level when doing a Repair Install (BTW if I recall correctly you could NOT repair an install with a "lower than installed" SP CD). Review this: http://michaelstevenstech.com/XPrepairinstall.htm You can try setting intelppm driver (and a few more ones) to start 3, only seemingly unrelated: http://www.911cd.net/forums//index.php?showtopic=22473&st=23 The "old" method was, with the XP install running on the "old" motherboard, go to device manager and delete EVERYTHING but: video keyboard mouse and shut down the system, then move the hard disk to the new motherboard, and WITHOUT letting it boot, start from CD the Repair install. jaclaz

It should be, in the sense that the tutorial is born with the idea of using "kosher" UNMODIFIED source .iso's, if (besides the actual integrated Service Packs) you actually modify them (like nlite, driverspack, unatttended and what not) it makes little sense, and another method, NOT using a .iso will save you the time to recreate the .iso. As well it is very possible that new KB's integrated may "break" the compatibility. Mind you I am not saying that any of the above will create a problem, only that it is possible that it may do so. jaclaz

No, you don't. Yes, but it has NOTHING to do with fonts and effects applied to that. The source (the tutorial page from which you copy) uses a DIFFERENT, "wrong" character codes for the quotes from the one that it is needed. The character code has NOTHING to do with font or effects applied to it. Compare with these (since you appear to use Word): http://www.ehow.com/how_6050557_delete-quotes-ms-word-2007.html http://support.microsoft.com/kb/206165/en-us Copy from the source. Paste into word. Select and change in ANY font you like and REMOVE the "italics" effect Do what is in the MS KB under "Replacing Existing Smart Quotes with Straight Quotes" Select and change in ANY font you like and add the "italics" effect Copy from Word Paste on command prompt However , I did my best you to explain the real cause of the issue to you, but if you are happy to think that it happens because quotes are in italic, you are perfectly free to do so. jaclaz