jaclaz

If you drink three or four glasses of Absolute vodka BEFORE trying polishing a CD the whatever is in your mouth will be VERY like Alcohol, .....but you would probably lose interest in the actual CD polishing.... jaclaz

I don't recommend that. I tried it a few months ago and was not impressed. It is basically experimental software for people who like to tinker. It's not usable as a normal desktop OS. But if you want to create some sort of very minimal bootable CD then you might give a try. Phil Actually, if you tried it a few months ago, you did not try latest (fully working) version, which was released October 8th, 2005: http://www.911cd.net/forums//index.php?showtopic=12326&st=53 I mean, what do you expect from Alpha/Beta FREE software, to work like a three years old COMMERCIAL software? NO, you NEED your own Win95 files and, from a legal standpoint, a valid LICENCE for BOTH Windows 95 AND Windows 98. jaclaz

Yes, most probably TESTDISK can do the trick: http://www.msfn.org/board/index.php?showtopic=50179 http://www.cgsecurity.org/testdisk.html make sure you READ the docs before attempting using it. jaclaz

Most probably you have not correctly setup the NTLDR/NTDETECT.COM/NTBOOTDD.SYS/BOOT.INI Read my post here: http://www.911cd.net/forums//index.php?showtopic=14250&hl= and related links. If you still have problems, please post a DETAILED list of info on how BOTH 2K and XP are installed, i.e. which drive, which partitions, etc. and I might be able to help you further. jaclaz

...hmmm, don't think it can be done, but have a look here where some info is gathering: http://www.911cd.net/forums//index.php?showtopic=13205&hl= jaclaz

Other possibilities (just for the record): dd for windows: http://uranus.it.swin.edu.au/~jn/linux/rawwrite/dd.htm Findpart, see my post here: http://www.911cd.net/forums//index.php?sho...877entry89877 @cdob The length of the NTFS (complete) boot code appears to be 6 (+1) sectors long, see links in my previous post here and in the one on the 911CD board linked to above, sectors after the first 7 (0÷6) are just zero byte filled. jaclaz

On both MS-DOS and FREEDOS, you need a Long File Name TSR: http://wiki.fdos.org/Main/LongFileNames http://www.geocities.com/jadoxa/doslfn/ Latest release and patches for freedos can be found on the home page: http://www.freedos.org/ http://www.free.oszoo.org/download.html Also latest version of DRDOS/OPENDOS: http://www.drdosprojects.de/ should be FAT32 and LFN compatible. jaclaz

Just as a reminder, you can use Ken Kato's VDK Virtual Drive Service: http://chitchat.at.infoseek.co.jp/vmware/ http://chitchat.at.infoseek.co.jp/vmware/vdk.html#top and (optionally) my pseudo-GUI for it, VIRTUAL DRIVE MANAGER: http://home.graffiti.net/jaclaz:graffiti.n...ts/VDM/vdm.html to load/read/write VMware virtual disks without VMware installed. Also newish releases of QEMU: http://fabrice.bellard.free.fr/qemu/ http://www.free.oszoo.org/ (optionally with the great GUI from Dave Reynolds): http://www.davereyn.co.uk/qemu.htm can create VMware compatible disk drives. jaclaz

98lite is a commercial product, you BUY it: http://www.litepc.com/ and follow instructions. Or you can try this FREEWARE alternative: http://www.911cd.net/forums//index.php?showtopic=12326 http://winimize.com/ jaclaz

Did you actually TRY it? Read here: http://www.msfn.org/board/index.php?showtopic=55456 jaclaz

Cannot say if it helps, but latest (8.00) version of Winimage supports reading EXTFS 2 and 3 partitions: www.winimage.com jaclaz

Why do I have a "DEJAVU" feeling ? http://www.msfn.org/board/index.php?showtopic=37402 (45 pages of posts on exactly the same topic) jaclaz

If you mean how do you put MBR BOOTABLE CODE into MBR, you can use: FIXMBR from recovery console or MBRFIX: http://www.sysint.no/Nedlasting/MbrFix.htm http://www.sysint.no/Nedlasting/MbrFix.zip and, optionally, my pseudo GUI for it: http://home.graffiti.net/jaclaz:graffiti.net/ http://home.graffiti.net/jaclaz:graffiti.n...X/mbrfix0.2.zip jaclaz

Sorry, deleted, I gave some ideas, taken from Rob Van der Woude's site but they are for NT/2k/XP only. jaclaz P.S.: Actually there is a way to read values in win95/98, through some peculiar "side effects" of some commands, see here: http://www.robvanderwoude.com/ http://www.robvanderwoude.com/regedit.html Skip to the Win95/98 section there are links to : http://www.robvanderwoude.com/amb_cdrom.ht...dromDriveLetter and CHOICE usage: http://www.robvanderwoude.com/choice.html

Interesting news, thanks. jaclaz

This is the best "nearly what you need" I know of: http://gabrieleponti.com/software/ Send To Toys 2.3 Of course to send a "open dos prompt" command you need an argument, if you select a directory, this add-on works like the Registry Tweak posted early, if you select a file, it opens to the directory where the file is and types the name of the file on the command line.This is of course VERY useful if the file is a .exe, .bat or .cmd, as you just add the (optional) parameters and hit enter.If the file is not an executable, you will need to use a bit of backspace. jaclaz

Well, that's a clear example of a "Virtual" drive! Seriously, the EB5290 is the standard "jump" code for NTFS partitions. The "jump" code tells where the next instruction is to be found, so EB=jump instruction 52=offset (i.e. distance where to jump) 90=nop (No operation, just a value to "pad" a byte) As 52 hex means 82 decimal, and 5B hex means 91, "your" bootsector jumps 9 bytes longer than it should, unless the boot code you have is not the original one. Best option, as I see it, would be to re-format that partition, but you can try checking the following (you need a hex editor capable of opening directly a disk or use a disk editor to copy that sector to a file, then use the hex editor: 1) If from byte 54 hex you find values FA 33 C0, the boot record seems ok and probably just the 52/5B is an error 2) If from byte 54 hex you do not find values FA 33 C0, the boot record is UNKNOWN. here is a reference to NT/2K/XP bootcode: http://thestarman.pcministry.com/asm/mbr/M...tail.htm#ntfsbr http://thestarman.pcministry.com/asm/mbr/NTFSBR.htm With that reference and a copy of the bootsector of another NTFS partition, you should be able to re-write manually the bootrecord wht an hex editor. jaclaz

Just to make sure, download this uti: BEEBLEBROX http://students.cs.byu.edu/~codyb/ And examine the Bootsector of that partition, in the "Jump" editbox you should have "EB5290" jaclaz

Yep, and it has already been reported as WORKING!: http://www.911cd.net/forums//index.php?showtopic=12326&st=55 (with some screenshots) jaclaz

Yep, I was referring to how the "real" NTLDR works. jaclaz

for the nth time Partition Magic is of NO use if the existing partitions/drives have errors! You might want to read this thread: http://www.msfn.org/board/index.php?showtopic=50179 jaclaz

Actually it is right there: http://www.grisoft.com/doc/289/lng/us/tpl/tpl01 or go to: http://www.grisoft.com/ click on "AVG Products" on the left AVG Free edition is 9th product from top. Any other "conspiracy theory"? jaclaz

Come on guys, original poster had his problem solved, and tubui's post was from APRIL I guess he solved his problem by now.... jaclaz

Though I am not an expert with WinPe, but maybe I can clarify some of the part related to bootpart. ANY partition, regardless if it is Primary or Logical, regardless if it is NTFS, FAT16 or FAT32, formatted under 2K/XP will have it's bootsector with the standard Microsoft code to load NTLDR. Once NTLDR has started, it reads BOOT.INI, where you can put two types of entries: 1) An arcpath to a Windows NT (NT here means NT/2K/XP/2003) install (i.e. something like multi(0)disk(0)rdisk(0)partition(1)\NTEXP="Windows 2000 PRO" /fastdetect) 2) A direct path to a copy of a RAW bootsector (i.e. something like C:\Bootsect.w98="Windows 98 Command Line" /win95) If used with entry of type 1) above, NTLDR will proceed booting the Windows NT files if used with an entry of type 2) above, NTLDR will work as a "chain" bootloader, giving full control to the RAW bootsector, just like it was the bootsector of the active partition. Bootpart was originally developed for people wanting to double boot NT and DOS 6.22, and evolved in the years. It can produce TWO kind of output files: 1) A standard bootsector: the syntax is following: bootpart <OS> <filename> Where OS can be (case insensitive): DOS622 MSDOS MS-DOS 6.22 I.D. MSDOS5.0 WIN95 Windows 95 I.D. MSWIN4.0 WIN95OSR2 WIN95SR2 WIN95OEMSR2 Windows 95 OEMSR2 I.D. MSWIN4.1 WIN98 WINME Windows 98 or Windows ME I.D. MSWIN4.1 NT WINNT WIN200 WIN2K WINXP Windows NT/2K/XP and 2003 VISTA WINVISTA Windows VISTA (BOOTMGR instead of NTLDR) OPENDOS OpenDos I.D. NWDOS7.0 (the "code" of the bootsector will change, but the "data" - like number of starting position of the partition, length, etc. - will be always the same, taken by your existing bootsector 2) A copy of a bootsector ALREADY on another partition: the syntax is following: bootpart <partition_number_as seen_by_bootpart> <filename> this will simply copy the bootsector of the selected partition to <filename> The same effect can be obtained by using a diskeditor, debug or dd. here is a link for debug: http://www.bcpl.net/~dbryan/ntfs-dual-boot.html (debug is already in the OS files) and here is one for dd: http://doc.rmplc.co.uk/linux/LDP/HOWTO/Lin...T-Loader-5.html (dd is already in ANY Linux distro, but there a few versions for windows too: http://uranus.it.swin.edu.au/~jn/linux/rawwrite/dd.htm If you add at the END of any of the two commands a string inside quotes, bootpart will add the entry to BOOT.INI. There is a section in the Winimage Forums dedicated to bootpart as well: http://forum.winimage.com/viewforum.php?f=1 where you can find many questions already answered. jaclaz

About service disabling, there used to be the blackviper site, (currently down), but you can find some of it here: http://web.archive.org/web/*/http://www.blackviper.com jaclaz