jaclaz

Things to read, that may be of use: http://www.911cd.net/forums//index.php?showtopic=21231 http://www.911cd.net/forums//index.php?showtopic=22975 There is an utility around that can change the UDMA support of the card and as well "flip" the "Removable" bit. Whether this solution: helps can be applied to the particular brand/make/model of card is for you to find out. (Your mileage may greatly vary ) jaclaz

Modified paragraph C4 of the first post to include this advice. To be picky not entirely accurate. If you only FORMAT the MBR won't be touched at all. If you FORMAT from Win9x (please read DOS) the PBR of the FORMATted partition will be replaced by the Win9x/DOS one, invoking IO.SYS and MSDOS.SYS. If you FORMAT first active primary partition of first disk you will also need to copy back to it the boot files, typically: DOS/Win9x: IO.SYS MSDOS.SYS COMMAND.COM NT/2K/XP/2003: NTLDR NTDETECT.COM BOOT.INI Vista/2008/7: BOOTMGR \boot\BCD And, if needed use BOOTPART to fix/repair the bootsector or PBR. In other words, FDISK changes the MBR, FORMAT changes the PBR. jaclaz

Here: http://www.msfn.org/board/index.php?showforum=157 jaclaz

Also, take this advice from an old man , use an old floppy drive. I don't trust "recent" floppy drive, something you bought new in the last 5 to 10 years and payed $5 to $7 apiece. Ideally you should have a few floppy drives, possibly salvaged from old "brand" PC. I have a 3.5" floppy salvaged from a Toshiba 5100 (a "portable" of the time) that weights a little more than 2 times one of the new ones, it's sturdy, and at least in my simple mind (and on field) more reliable than those cheap thingies. Besides that, every floppy drive can (and is) slightly mis-aligned, let's say that you have a "left misaligned" floppy drive. Anything you write on a floppy with it will be readable on the same drive and on all floppy drives that are perfactly "centered". As soon as you put that floppy in a "right misaligned" drive, it won't be read properly anymore. If you have a few floppy drives, it is probable that some will be misaligned the same way the one on which the floppy was originally written was. Unfortunately, I think that the most you can try is cleaning the heads, without specific tools. Some reference: http://www.accurite.com/FloppyPrimer.html jaclaz

Or use, as it has been done successfully for more than 15 years, a small FAT16 boot partition (with boot files) and any number of logical volumes inside Extended, one for each OS..... jaclaz

Just for the record, rat's nests have been historically proven to be actually an efficient, working solution (for rats).

The SIS groveler is a feature of the "Server" version of MS Windowses, AFAIK. You cannot have it "independently", thus you would need a license for the server version. My guess is that the Server 2003 SIS can be actually installed on XP, if you manage to install the whole RIS: http://www.windows-xp-services.com/windows...e-groveler.html But I don't think it will be an easy task, if possible at all. Sorry for not being of help. jaclaz

It is not needed, not required (or if required, possibly NOT allowed), see Rule #13: http://www.msfn.org/board/forum-rules-upda...ead-t18408.html I guess your thanks are enough. jaclaz

@ilko_t @Ikky_Phoenix Thread splitted: http://www.msfn.org/board/winsetupfromusb-...ce-t137800.html jaclaz

http://www.911cd.net/forums//index.php?showtopic=23269 http://www.boot-land.net/forums/index.php?...ic=9002&hl= jaclaz

Nice. Just for the record, grub4dos or Syslinux/memdisk can map a floppy image to (fd0) (please read as A:\) allright. As long as the OS inside the floppy is a "protected mode" one and there are no programs that use undocumented ways to access the floppy, it will work allright. jaclaz

See if this is understandable. jaclaz Demo_revised_2.zip

I am completely failing to understand the question. I don't understand. We don't have a or b, nor c or d, we have: Driver Tech We don't have a single "24" in all the sheet, we never talked about break deduction. This is more understandable (maybe): As I understand it: Designation 1 (Driver?) is payed: on weekdays up to 8 hours "standard" rate, everything above 8 hrs as "overtime" (conventionally OT 1.5) on saturdays up to 4 hours "standard" rate, everything above 4 hrs as "overtime" (conventionally OT 1.5) on sundays and public holidays anything is payed as "holiday overtime" (conventionally OT 2.0) The deduction for break does not makes sense to me, at least in this case: This would mean that if the driver works 2 hours on sunday morning, from, say, 10.00 to 12.00 he is payed one hour only. Isn't there a limit to the total amount of hours per day? Is it 10 hours per day? Or there is an "overtime beyond limit per day" (conventionally OT 3.0)? Isn't the break deduction tied to a minimum amount of hours worked in the given day? Or there is a minimum of worked hours per day (say 7 hours per day minimum)? As I visualize the sheet, the "main" condition is if the given amount of hours have been worked in either of three cases: workday saturday sunday or holiday once decided which day is it, the Vlookup simply searches in the corresponding designation table what should be paid. I.E., and with reference to the "Demo_revised.xls" : in sheet VLOOKUP_example you insert between Columns B and C whatever formulas/methods to transform the "TIme in" and "Time Out" in "Total Hours" AND decide whether it is weekday, saturday or sunday. Thus the total hours in Column C become the result of the above. In the "Normal" and following columns you EITHER: make a VLOOKUP to three different tables, i.e. instead of a sheet called "Tables" to three sheets called "Table_workdays", "Table_saturdays", "Table_holydays" Or you make a "cumulative condition". Example: Say that "designation" equals to "Driver" and that the given day is a "weekday", you "concatenate" the condition, i.e. the lookup value becomes either: Driver_weekday Driver_saturday Driver_sunday this way you have a single "Tables" sheet. Give me a few minutes, and I'll post an example of the above. jaclaz

Well, now I am completely lost. I am probably just a bit tough, or tired, or both but your explanation made things foggier that I thought they were before. Can you, when you have time, post a COMPLETE example (as opposed to bits and pieces scattered in one liners on three different threads, one on boot-land and two here on MSFN) for each of the two approaches? jaclaz

But are you looking for a freebie or for a Commercial solution? If the second: http://www.open-e.com/products/ jaclaz

I am not sure to have any clearer understanding than I had before. Unless I am grossly mistaken the attachment contains only a bunch of Excel sheets with NO formulas, but values. What I am I supposed to do with it? Printing it and attaching it to the wall? Nice colours, BTW. jaclaz

JFYI: http://www.msfn.org/board/nuhi-working-mic...ft-t133617.html jaclaz

Check the CD, or however your source against the list of files in a "normal" CD: http://www.msfn.org/board/cannot-access-cd...les-t91907.html You should have ALL those files (and if you have a slipstreamed SP possibly some more) jaclaz

On a side note, it is rarely the case of a PC that cannot run a PE 1.x (please read UBCD4WIN) , given that the appropriate drivers are added to the build. VistaPE is a Winbuilder project. Winbuilder has a dedicated board: http://www.boot-land.net/forums/ A copy of the WAIK is needed anyway AFAICR. But I see that you already got there: http://www.boot-land.net/forums/index.php?showtopic=8984 Of course without spending two minutes to search a bit before posting. DriveimageXML has known problems under VistaPE: http://www.boot-land.net/forums/index.php?showtopic=3565 http://www.boot-land.net/forums/index.php?showtopic=5028 It is NOT advised for a new user of VistaPE. I would rather try to build an XP based project adding the drivers for your machine. jaclaz

How I would like it if people wouldn't speak using codes .... C=Chipset CP=CPU L=LAN M=Mass Storage W=Wlan jaclaz

Very good! May I ask why the need to map XP_INST.IMA: map --mem /Inst/XP_INST.IMA (fd0) map --mem /Inst/XP_INST.IMA (fd1) twice? It is somehow needed to "fill" both A:\ and B:\ drive letters? jaclaz

Network cables you buy are normally "patch" or "straight through" as they are meant to go from a Lan card to a Hub or Switch. To connect two Lan cards you need a "crossover" cable. Read here: http://www.littlewhitedog.com/content-8.html There are handy "adapters" to make a "patch" cable into a "crossover" or viceversa, example: http://www.usbfirewire.com/Parts/rr-et-crossoveradapter.html jaclaz

A "normal" CD/DVD drive on notebooks has a tray like this one: You can mount this type vertical allright. The CD/DVD is kept by three little spring hooks. ANY Slim-line CD/DVD (anything that has not a "square" plan but rather a "corner cut out" on one side) has a 50 pin JAE connector, see these: Of course laptops have this connector directly on the motherboard, but you need a converter board (similar to the one depicted above) that has on one side the 50 pin connector and on the other side the appropriate connectors, depending on the drive type (IDE/PATA or SATA): 40 PIN IDE/PATA + POWER: http://www.8starshop.com/en/50-pin-laptop-...de-adapter.html OR SATA+POWER (this is the type you will need): http://www.sourcingmap.com/slim-dvd-driver...er-p-17005.html The POWER connector is the one used for floppy drives, if you don't have one on your PSU, you will need a converter, like this one: Read about SATA connectors here: http://en.wikipedia.org/wiki/Serial_ATA Basically you'll have on your "desktop" case a "desktop" SATA that will use a 8 (please read as 7) pin connector, and a "normal" SATA cable. The converter seen above is designed to mount laptop CD/DVD's on desktops, thus the SATA connector will be the "normal" one, this one: http://en.wikipedia.org/wiki/Serial_ATA#Data FORGET about SATA power connectors, you WON'T need them for the CD/DVD drive. If you have a SATA hard disk, you may need a Molex to SATA power adapter, like this one, you DON'T NEED to get another PSU: or this: http://www.sourcingmap.com/pin-ide-pin-ser...er-p-24149.html I hope this clears your doubts. jaclaz

Well, that's strange. The guide has proved to work in several hundreds of cases for "AS". The other thread worked for the "NS", at least in a few cases. Maybe you have a firmware "HP24"? http://forum.hddguru.com/seagate-7200-firm...are-t11755.html Did you "wait enough" after power on/before the Z? Check this guide also: http://sites.google.com/site/seagatefix/Home jaclaz

Yes. Will it work? See if this works: http://www.msfn.org/board/unlocking-termin...te-t129551.html Read CAREFULLY! It is not clear WHICH are the terminals to be shorted. Be very careful to NOT short anything else. Read, re-read and re-re-read the info, make sure you find a "safe" way to attempt the shorting, do some tests with the hard disk NOT connected to power. Your mileage may vary. Doesn't the "normal" approach work? Maybe the Italain translation of the original guide helps: http://www.msfn.org/board/riparazione-seag...no-t129366.html The currently easiest and all-in-one tutorial is here: http://www.msfn.org/board/debricking-seaga...87.html&hl= jaclaz