jaclaz

Short (and rude) answer: NO.Long (and polite) answer: Yes there are a lot of good and not so good tutorials, unfortunately compiling an app is something really difficult by itself, and doing so with cygwin or MinGW libraries is even more so. To add some complications to it, cdrecord is a VERY complex Source, so that you really should begin with much simpler apps. Just have a look at this (very old) reference to have an idea of the nightmare it sometimes is: http://www.delorie.com/howto/cygwin/mno-cygwin-howto.html I really don't want to put you down, but to be able to successfully compile a source with Cygwin, a tutorial is not really enough you unfortunately need a rather vast knowledge of both the linux and Win32 worlds, besides experience in programming ..... just search on google for "compile cygwin howto" or "compile cygwin tutorial" (without quotes) and you will find lots of tutorials, most aimed to a particular program, but that nonetheless give also "general" instructions. Good luck , I was never able to overcome the steep path to learning how to do that, properly configure the system, have all the dependencies and libraries in the right places, etc., maybe just because I didn't try hard enough, but I know people that do that like drinking a glass of water, I guess that here is a sort of Catch 22 in this matter jaclaz

Pre-compiled last cdrtools Win32 port (Cygwin): http://www.sbox.tugraz.at/home/t/tplank/ Elder "special" cdrtools Win32 port (MinGW): http://www.bcdwb.de/downloads/cdrtools.htm jaclaz

Should be this one: http://www.msfn.org/board/index.php?showtopic=69101 jaclaz

Sorry, I'm not sure I got it. Do you need the pinout for a standard IDE/ATAPI connector? Here it is: http://www.interfacebus.com/Design_Connector_IDE.html http://www.bbdsoft.com/ide.html http://pinouts.ru/DiskCables/IDE_pinout.shtml http://pinouts.ru/HD/AtaInternal_pinout.shtml jaclaz P.S.: Pin may look spade-shaped, but it should be just square (it depends on how you look at it )

Yep, most probably the guys at MS dropped support for .hlp files to reduce size of Vista installation.... jaclaz

Usually? @wild weasel I guess that you are talking about the project LLXX announced here: http://www.msfn.org/board/index.php?showtopic=74797&st=4 and that is still in the works according to this: http://www.msfn.org/board/index.php?showto...89278&st=10 jaclaz

It looks like some kind of problem related to it being a DYNAMIC disk... http://support.microsoft.com/kb/222189/en-us http://www.dbforums.com/t675935.html jaclaz

Actually for such tasks Word can do it: 1) run search and replace with search "<" and replace "^t" (without quotes), this will replace every occurrence of < with a TAB 2) run search and replace with search ">" and replace "" (i.e. have the replace box empty), this will replace every occurence of > with nothing. 3) Select the list and use "Convert text to table" making sure to use TAB as the delimiter. 4) either delete the column before the e-mail addresses and convert the table back to text or select only the column with e-mails and paste it in another document (either Word or, as suggested, Excel) Alternatively, you can save the Word file to "plaintext" with a .csv extension and then use Excel as uid0 suggested. jaclaz

The letter assignment should be due to the type of partition. Please find here some related info: http://www.msfn.org/board/index.php?showtopic=23484 http://www.msfn.org/board/index.php?showtopic=67395 http://www.msfn.org/board/index.php?showtopic=53177 jaclaz

Yes, the same thing can happen with your login password on most system. The point I was trying to make is that there is no actual need to change the default key, and if you go on and change it and your memory is so bad that you cannot remember it, you can stick a Post-it™ near your screen with the "new" key written on it or just try the few keys that can be assigned the function. All in all, I don't see this as a major problem or as a reason to prefer another VM to Virtual PC (size of install, speed and compatibility with different booting methods appear to me as a more accurate comparison area). jaclaz

Yes , though rather faint, you can sometimes hear the screams of the poor cursor, hopelessly trapped inside the VM window..... ....the horror of it all.... ...how cruel were the Connectix/Microsoft guys.... jaclaz

Yes, unless it uses some .DLL functions not present in the Win95 version of * comdlg32.dll * shell32.dll FYI, a section of the forum at bootland is now dedicated to mindows: http://www.boot-land.net/forums/Winimize-f53.html where maybe you can ask for questions not answered here. The developer "winimizer" posts there too, from time to time. jaclaz

Yep, the page has something wrong today, it seems like it reloads continuosly. Direct links (respectively): http://web.tiscali.it/axart/soft/aedit50.zip http://web.tiscali.it/axart/soft/aedit4_full.zip http://web.tiscali.it/axart/soft/aedit4.zip http://web.tiscali.it/axart/soft/zipdlls.zip http://web.tiscali.it/axart/soft/aesc.zip http://web.tiscali.it/axart/soft/aep.zip Features (v5.0 version): http://web.tiscali.it/axart/feaeng_ae.html jaclaz

aedit, rather old but good word processor that reads MS Word files (and saves in .rtf): http://web.tiscali.it/axart/ http://web.tiscali.it/axart/english.html jaclaz

Or possibly with MBRwiz: http://mbrwizard.tripod.com/ or Beeblebrox: http://students.cs.byu.edu/~codyb/ Cannot say if these and the ones suggested by Sonic run under Vista, or you are using XP? jaclaz

Hmmm...., I don't think it's possible, but you can try to experiment lowering the value of in BOOT.INI, a value of 0 should be equal to "directly" boot the default OS, but maybe, just maybe, if you press the [DOWN ARROW] key at the right time, you might be able to select the other entry. With a value of 1, you will be able to use the key, but the BOOT.INI screen will probably be visible too much time for your tastes. A possible alternative, for Ghost recovery, cannot say if it is possible to extend it use to other situations, is this rather complex procedure: http://www.911cd.net/forums//index.php?showtopic=18480 but it involves using a third party bootmanager, drive won't be "standard" anymore. More similar reference: http://www.msfn.org/board/index.php?showtopic=47773 http://www.goodells.net/dellrestore/ jaclaz

Now I see. Nice trick, I always directly edit boot.ini post-install with Notepad, I would have never thought of this, but I can see the usefulness of it. jaclaz

@E-66 As I see it, keeping things as "standard" as possible, unless something "different" is REALLY required, is always advisable. And the thought of being able to fix things with a simple DOS/Win9x floppy or bootCD, should always been taken into account. What I would do in your case: 1) Have the Primary Active partition formatted as either FAT16 or FAT32 (to have maximum compatibility), this is a solution I use since more than 10 years, and experience confirmed the usefulness of such a setup, see this: http://www.msfn.org/board/index.php?showto...mp;#entry581401 2) Install WinXP normally in one of the Logical Volumes inside Extended Partition 3) Download Grub4Dos from here: http://grub4dos.jot.com/WikiHome extract from it the grldr file and copy it to the Primary partition (drive C :\ ) 4) Copy and paste the following in Notepad and save it as menu.lst (again on drive C :\ ): [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /fastdetect C:\GRLDR="Grub4Dos" As you see, you didn't modify anything in the MBR nor in the bootsector, you only added a boot option to the "standard" NTLDR/BOOT.INI boot process. The two entries in menu.lst allow you to either go back to the "standard" NTLDR/BOOT.INI (should you change your idea) or to boot from DOS/Win9x files. Till now nothing really new, the same can be done easily with the help of Bootpart: http://www.winimage.com/bootpart.htm and just the standard NTLDR/BOOT.INI But if you read the Grub4Dos documentation (actually at the moment rather scarce) and if you go to the 911CD Forum and search on it for posts with "Grub4Dos" in them to get some ideas and hints, you will soon find out the enormous potentiality you have in your hands, here are a few good starts: http://www.911cd.net/forums//index.php?sho...c=18838&hl= http://www.911cd.net/forums//index.php?sho...c=18045&hl= http://www.911cd.net/forums//index.php?sho...c=18846&hl= A few basic examples: You install a BartPE on C :\ ?, just add this in menu.lst: title BartPE find --set-root /minint/setupldr.bin chainloader /minint/setupldr.bin You have floppy boot disabled in BIOS? Just add this: # This simply boots a floppy disk from your # physical floppy drive. title Boot Floppy on (fd0) chainloader (fd0)+1 rootnoverify (fd0) You have CD boot disabled in BIOS? # This simply boots a CD from your # physical CD drive. # Cd must be a BootCD of course title Boot CD on (cd) root (cd) chainloader (cd) You want to boot from a Ghost (super)floppy image?: # This is how you boot a floppy image # stored on a FAT/FAT32 partition. # Replace ghost.img to whatever image you desire to boot. title Boot Ghost 2003 (ghost.img) find --set-root /ghost.img map --mem /ghost.img (fd0) map --hook chainloader (fd0)+1 And the above are just a few of the possibilities..... jaclaz

Things that come to my mind (pardon me if they are too "basic" for your level of knowledge): 1) Incorrect BIOS settings (need to set HD detection to "AUTO" or manually change it to the right drive) 2) Incorrect master/slave or CS setting on the drive(s) (check jumpers) 3) Bad cable(s) (try with another one) 4) Incorrect connection of the cables, if they are the 80 conductor ones Master and slave are coded as "black" and "grey" respectively, while Motherboard side is "blue": http://www.pcguide.com/ref/hdd/if/ide/confCable80-c.html 5) Conflict with the "other" CD drive (disconnect it temporarily) As a side note, and as a general rule, when Ghosting or however transferring large amounts of data between hard disks, having them on two different IDE channels is a good idea, to avoid possible bottlenecks on the single channel. jaclaz

Yes. If you are quite confident that the MBR and the first few sectors of the HD have not been corrupted you can make a copy of them with dd under linux and later restore them with either dd for windows: http://uranus.it.swin.edu.au/~jn/linux/rawwrite/dd.htm or the DSFOK toolkit: http://www.ozemail.com.au/~nulifetv/freezip/freeware/ I don't remember how many sectors grub uses, but if you backup the first 63 sectors you are on the safe side. An alternative could be using the grldr from Grub4dos to chainload Linux from the "normal" NTLDR/BOOT.INI: http://grub4dos.jot.com/WikiHome jaclaz

No, actually it is the other way round, though, probably, for your use the 800dpi is enough. A higher dpi (i.e. resolution or density) of the sensor means that the sensor can appreciate a SMALLER movement, as an example if you move your mouse one inch: on a 800 dpi mouse: the movement will be "sensed" as 800/800=1" on a 1600 dpi mouse (I am using 1600 just to simplify the math): the movement will be "sensed" as 1600/1600=1" So, NO difference. But if you continue the movement a very little bit and then reverse it: the 800 dpi mouse will "toggle" between 1" and 1"+1/800 the 1600 dpi mouse will ALSO pass through the value 1"+1/1600 while going between 1" and 1"+2/1600 (=1"+1/800) The actual movement of the mouse is translated into movements of the cursor on the screen with a ratio (adjustable via the driver settings, and for the sake of the reasoning, not taking into account acceleration settings), just as an example the same 1" movement of the mouse produces, say, a 4" movement of the cursor, i.e. the ratio is 1:4. If you have a 17" monitor (diagonal measure), the actual screen (viewable area) will be roughly (WxH) 13"x10", so, in the case of a vertical movement, the minimum amount you can move the cursor becomes: 10"/4/800=1"/240 with the 800dpi and 10"/4/1600=1"/480 with the 1600dpi Of course, if you lower the ratio you get more precision of the cursor (but you need wider movement of the mouse), whilst if you increase it, you "lose" precision (but you move less the mouse). So, given that the 800dpi is enough in normal use, you can see the increased precision of the 2000dpi as a way to put less strain on the hand using the mouse OR being able to work on smaller mousepad with the SAME sensitivity OR being able to work with enough precision on an image without magnifying it on the screen too much (provided that your eyesight is good enough ) while being able to quickly move the cursor on the menu or toolbars. Another factor that should be taken into account, as said, is the ability to separately set resolution in the x and y directions, and more generally, the quality of the driver. (in this case related to wideness of settings and "response" to them) Moreover, not all hands are the same, you might find a particular shape of the mouse as very comfortable while I might find the same one making me hold the hand or fingers at awkward angles.... Sampling rates (i.e. the number of times the sensor is actually read per second) should not be a problem for Photoshop use, while of course is very important for gaming where mouse movements are FAST. jaclaz

...and may I ask what this has to do with boot.ini? Thread title: jaclaz

Sorry, I don't want to worsen the already made confusion on terms, but actually some of the above concepts appear to be incorrect. An Active partition is one that has a "bootable" flag in the MBR. This means that only Primary partitions can be made bootable. When you boot the BIOS looks in the MBR of first drive and search for bootcode on the partition marked as bootable in the MBR, see here: http://www.goodells.net/multiboot/principles.htm A "Logical Partition" should be more properly referred to as "Logical Volume inside Extended Partition". The Extended Partition has an entry in MBR that redirects to the EMBR where the actual entries for the Logical Volumes (read Logical Partitions) are. As long as a proper bootloader (in NT/W2K/XP/2003 NTLDR+NTDETECT.COM+BOOT.INI) resides on an active primary partition, it can boot a system (the /WINNT or /WINDOWS folder) residing on ANY accessible partition, regardless it is primary or logical. On the other hand, as a very simple "security feature", you can have a disk with no active (and not even primary) partitions and boot from a removable device such as a floppy or USB stick, where these bootloader files are: http://www.xxcopy.com/xxcopy33.htm If you install, INSTEAD of the "Standard" MBR code a BOOTMANAGER, you can also boot some Operating Systems (including NT/W2K/XP/2003) directly from a Logical volume, if you fix the hidden sectors with the correct values: http://www.goodells.net/multiboot/ http://www.goodells.net/multiboot/ptedit.htm The easiest way to setup a disk for single boot or simple multiboot (and to a certain extent, as I see it, the safer) is the way E-66 suggested, check also this posts of mine: http://www.msfn.org/board/index.php?s=&showtopic=47182 http://www.msfn.org/board/index.php?showtopic=33964 jaclaz

Thanks for the heads up! jaclaz

Well, it was an easy one, happy it worked. jaclaz