jaclaz

Here: http://www.motherboards.org/mobot/drivers/Transcend/TS-AKT4%257CB/ http://www.driver-central.com/TS-AKT4B_BIOS-11569-aaa4-driver.html http://www.motherboards.org/files/manuals/129/E-AKT4.PDF http://www.motherboards.org/files/manuals/129/E-AKT4A.2.2.PDF http://www.zdnet.de/aktuelle_treiber_mainboard_bios_basic_input_output_system_transcend_index-39002352-676o0o0o0o39048905-1.htm http://www.zdnet.de/aktuelle_treiber_mainboard_bios_basic_input_output_system_transcend_ts_akt4_b_download-39002352-97883-1.htm jaclaz

WHY? It seems to me like you are confusing Windows 98 USB drivers with DOS drivers, the latter need not (and there is NO reason for) being in System folder. jaclaz

Do not assume too much. It didn't work for you with the particualr converter you had, no point in telling people not to do something that has worked and does works perfectly, with the appropriate board, as it is simply not true. Read here: http://www.msfn.org/board/index.php?showtopic=128807&st=2338 jaclaz

Board search is not working properly (and this is serious ). If you search for all posts by jaclaz, this recent thread does NOT come out as result : The results are 8 pages (while jaclaz has approximately 5,674 posts - the old board "limited" the search to last 1000 posts) Also, I seem like not being able to have "Show posts as results" from the search form. The new version of friendly names, is still not working fully. Link to single posts, like this one: lead to the top of the page where the post is instead that on the actual post, like: The "old" addresses do work: http://www.msfn.org/board/index.php?showtopic=128807&st=2338 http://www.msfn.org/board/index.php?s=&showtopic=128807&view=findpost&p=904788 the above (which works), translates in the browser toolbar to: identical to the one produced by the "link to post" above, but it does not work. jaclaz

The fact theat the filesysttem(s) on a HD is/are not accessible does not mean that the HD is not. The HD (if operational) will be mapped to a \\.\PhysicalDriven. Since you originally used: You can now use: You must think of the tools having a syntax (simplified) like: dsf (get) out of <device or file> <starting from> <and up to> (and save as) <device or file> and dsf (get) inside of <device or file> <starting from> <and up to> (the contents of) <device or file> Of course you should make sure that the device you are writing to, the n, is the right one. Or you can extract just the MBR and the last sector (the PBR) out of first2049mod.bin and write them to the HD (if you connect the Hd, since it alrady contains a partition table, you should get it connected as both \\.\PhysicalDriven AND to a Logical Drive - a drive letter which you can see in Explorer - but that when you click on it will ask you to format the drive). So: dsfo C:\dsfok\first2049mod.bin 0 512 C:\dsfok\theMBR.bin and dsfo C:\dsfok\first2049mod.bin -512 0 C:\dsfok\thePBR.bin will produce respectively the MBR and PBR, sized each 1 sector or 512 bytes, which you can then write (again respectively) with dsfi or, maybe more easily with Hdhacker: http://www.dimio.altervista.org/eng/ to \\.\PhysicalDrive and LogicalDrive The latter: dsfo C:\dsfok\first2049mod.bin -512 0 C:\dsfok\thePBR.bin can be written as: dsfo C:\dsfok\first2049mod.bin 1048576 0 C:\dsfok\thePBR.bin or dsfo C:\dsfok\first2049mod.bin 1048576 512 C:\dsfok\thePBR.bin as when <and up to> equals to 0 it means <up to the end of file> I hope I am not confusing you more than needed, the PhysicalDrive represents the whole device, no matter if partitioned/formatted or not and it's first sector is the first sector of the device, LogicalDrive represent ONLY a part of the device, and ONLY the part that is defined in the partition table (the partition) NO matter if the partition is formatted or not. The first sector of LogicalDrive corresponds to the address given in the partition table, in your case 2048. jaclaz

First thing don't panic. Let's tackle this with some calm, I can understand maybe half of what you posted. An external hard disk is a hard disk, no matter which filesystem(s) are on it. There are softwares able to read MAC filesystems: http://www.boot-land.net/forums/index.php?showtopic=8587&hl= Maybe you should describe the problem you are having with some details, and one thing at the time. jaclaz

@supem It would be better if you start a new thread, titled "How to create a bootable stick under Win98" or similar, so that we can discuss the specific issue and hopefully find a solution without mixing the issue with this generic "drivers" one. jaclaz

Good to know we have yet another happy bunny. http://www.msfn.org/board/index.php?showtopic=128727&st=10 Basically: the only two problems your partition apparently had were: wrong partition ID in partition table (06, aka "DOS" FAT 16 CHS mapped instead of 07 HPFS/NTFS) missing (wiped or filled with 00's) first sector of the NTFS bootsector And a third one (which is you lied as that partition was originally created under Vista or 2008 or Windows7 - or however, it's bootsector was later modified by MBRFIX.exe or bootrec.exe, or a similar tool in order to invoke BOOTMGR instead of the NT/2K/XP/2003 NTLDR). Vista and later, unless a Registry fix to make them behave like previous OS, create a partition "aligned to 1 Mb", for a number of reasons you may want to read/learn reading here: http://www.boot-land.net/forums/index.php?showtopic=9897&hl= In ther words, while NT/2K/XP/2003 normally create a set represesenting a whole cylinder of hidden sectors (63) Vista and later create a set of 2048 of them. (2048*512=1,048,576 =1 Mb) The first sector after the hidden sector is the bootsector, in this case 2048+1=2049 <this is why I wanted to have a look at first2049.bin, and of course 2049*512=1,049,088 Since last sector of first2049.bin was made of all 00's, I asked you to produce the first5000.bin, in order to check whether that a bunch of sectors after the 2049th werer blank as well or contained some data. The actual "whole" bootsector on a NTFS filesystem is actually 16 sectors long, so I could have asked you to produce 2048+16=2064 first2064.bin or, at the most, to check some other 100 sectors, a first2164.bin, but 5000 is a nice, round number, and allowed me to check also for some other things (since the partition ID was definitely "wrong" and you had already lied to me it was possible that the partition was actually a logical volume inside extended and that the missing 2049th sector was - instead of being a bootsector and EPBR, in which case the actuall bootsector may have been another 1 Mb further in the disk). For a quick reference of what an EPBR is, read this oldish, but still useful partition primer: http://www.ranish.com/part/primer.htm With first5000.bin in my hands I could check that 2050th sector was actually the second sector of a NTFS "Vista" bootsector, and that the following sectors made sense. So, since the LBA partition data in the MBR StartLBA=2048 appeared correct, I assumed that also the NumSectors=234436608 were also correct. If the above was true, the partition should have ended at LBA 2048+234436608=234438656. From the output of your initial dsfo command, I knew that the whole disk was 120034099200 bytes, i.e. 120034099200/512=234441600 sectors. Now, 234438656-234441600=-2944 so the partition should have ended 2944 sectors before the end of the drive. NTFS has a "failsafe" mechanism that creates a copy of the bootsector of the partition at the end of it. So, I could well have asked you for 2944+1=2945 last2945.bin, and check if the first sector of it was actaully a first sector of a NTFS bootsector, but since I already had mentioned a nice, round number of 5000, I asked you for a last5000.bin. I found the bootsector where i expected it, at offset -2945 sectors, and simply copied it and pasted over 2049th sector of first2049mod.bin (a copy of first2049.bin), then modified the partition ID in first sector of first2049mod.bin from 06 to 07. Checked if the data in the "new" bootsector made sense with the data in the parition table, and posted it. Tools used: TinyHexer Structure viewers by jaclaz: http://www.boot-land.net/forums/index.php?showtopic=8734 Knowledge needed: understanding the contents of this site (yes, everything in the /mbr/ ) http://mirror.href.com/thestarman/ http://mirror.href.com/thestarman/asm/mbr/index.html familiarity with a hex editor (TinyHexer in this case) some experience with MBR's, PBR's EPBR's and the like. (first and last point will take some time ) But no secrets and no magic tricks, only some smoke and mirrors. jaclaz

You mean a bootable USB stick? Maybe (just maybe) there could be another way. You can see your USB device under Win98 GUI, don't you? Can you try running in Win98 this tool Swissknife: http://www.compuapps.com/Download/swissknife/swissknife.htm and check if it sees the USB device? jaclaz

YES . http://homepages.tesco.net/J.deBoynePollard/FGA/questions-with-yes-or-no-answers.html There are "different kind" of links. The ones that always work is the "old/plain" one specifying the thread number, see here: page__p__877548#entry877548 (with the newest update, syntax has changed a bit again, the above is the "new" kind of links, below is the "old/plain" one: http://www.msfn.org/board/index.php?showtopic=137119 http://www.msfn.org/board/index.php?showtopic=137119&st=2 to the same post/topic. jaclaz

Search seems to behave differently. Example: to get to quickly know if there were replies to any of the threads where I posted, I was used to go to search and look for all posts by user jaclaz. The result was: all the stickies (where I posted) first all the other threads (where I posted) with the name of last poster To have a similar result you need to have now: in personal settings "Show results as a forum" in Search the checkbox "Do not show a post preview" The stickies are not anymore "floating" to the surface. I don't see a problem in this , but it may be needed to put somewhere a sticky explaining the above for people that suddenly have "different things showing up" as result of a search. jaclaz

My crystal ball being again in the shop for tuning , I cannot see your computer, and cannot even determine whether it is a desktop or laptop, and not even see the bus it is using, IDE/ATA, SATA or SCSI. Different connectors may have different problems, as well as different cables (if any). Maybe if you give some details.... jaclaz

Yep but the problem is actually in the change, which happened with Vista and is kept with 2008 and Windows 7, but that XP does not "like/understand". I guess one of the very rare occasions in which Vista itself is innocent. jaclaz

http://www.imdb.com/title/tt0104952/quotes Wrong conclusion . Right conclusion : Again, though I hate to use popularity or statistics as metrics, that method has worked for years with at least (my direct experience): English Spanish Italian German French sources, plus, since noone ever before you protested, probably any other language known to humanity. B) You have in your hands a "botched" source, case dismissed. jaclaz

NOT the answer you are looking for, but maybe interesting to you. Be aware of possible issues if multibooting with non-vista/2008/7 OS (please read as XP and possibly 2003): http://www.boot-land.net/forums/index.php?showtopic=9897&hl= jaclaz

OK. Try the attached file. It is a copy of first2049.bin with the last sector being the NTFS bootsector copy from last5000.bin. Unzip and apply as follows: (please note how you are now using dsfi and NOT dsfo) After you have applied the file to the image, try running again TESTDISK on the image, you should be able to find the partition AND to see the files. (you shouldn't need to do any repair) If the above is OK, then try mounting the image with IMDISK. jaclaz first2049mod.zip

NO , they are completely different errors (and causes for it). NO . There can be several causes for the "click of death", most solutions for them they are simply NOT doable "at home", and the others are NOT documented on this thread. You can try applying the "LBA0" fix, not because the fix or problem is in anyway related to the "click of death", but because the procedure may "refresh" some data that may be connected with the clikcking. Unfortunately your only hope is trying at hddguru Forum: http://forum.hddguru.com/ it is possible (but not probable, again unfortunately) that some of the guys over there will help you. jaclaz

FreeDOS Fdisk freefdisk: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/fdisk/ The whole point on which seems like we are misunderstanding each other is that for the DOS way you make the internal hard disk bootable in DOS, and copy to it the Source files (\I386\ directory) and then run from it the Setup. The USB stick is taken out of the equation very soon, after the files are copied to the internal disk. The method, though awkward and not "easy" has worked for years, at the time it was very common, on a "normal" machine to have DOS, and, to speed up the installation (and being not nagged to insert CD later if some features were not installed in first instance) to copy from the CD the \I386\ directory on HD and run WINNT.EXE from the HD. jaclaz

If anyone has the problem, he should get the already given floppy: http://johnson.tmfc.net/dos/usbdrv.html which contains the same panasonic drivers+a few others (DUSE,Iomega) updated when compared from those in the 2003 article, the ones in the given link on Panasonic site are v2.06, the ones in the given link are v2.15, which should be faster/better. However, this is the reference to get v2.06 and v2.15 and use them: http://www.computing.net/answers/dos/dos-mass-storage-driver-usbaspisys/15261.html jaclaz

Can we have the "classic" skin? jaclaz

I think that one of the "less clear" things in the "Windows business" are Fonts. The information about them is on half of the internet, but often (read ALWAYS) it is not clear. Take this (nice BTW ) page for example: http://www.mydigitallife.info/2008/11/20/h...command-prompt/ And this one: http://windowsitpro.com/article/articleid/...le-windows.html Evidently more or less copy/paste from: http://support.microsoft.com/kb/247815/en-us And the questions are: is there a program that can go through a Fonts directory and point out these characteristics of the fonts? is there any FREEWARE program that can change the charactristics of, say, a fixed pitch font but NOT FF_MODERN to FF_MODERN or a "converter" kind of app? if yes, where is it? Also, can please someone explain what the heck is a "negative A or C space"? jaclaz As a Side note: Fonts that have these characteristics: White Rabbit: http://www.dafont.com/white-rabbit.font Found on: http://www.mydigitallife.info/2008/11/20/h...command-prompt/ Consolas Vista or 7 or Power Point 2007 Viewer: http://labnol.blogspot.com/2007/03/downloa...ts-legally.html DejaVu Sans Mono http://dejavu-fonts.org/wiki/index.php?title=Download Droid Sans Mono http://damieng.com/blog/2007/11/14/droid-s...eat-coding-font Found on: http://blog.wolffmyren.com/2009/02/26/nece...command-window/

What do you mean by IP range? The subnet mask? Or the Lan card IP? Something like this: http://www.robvanderwoude.com/ntfortokens.php You can parse the IPCONFIG /ALL command output. jaclaz

You won't like the answer. You need: to have LucidaConsole (or another TTF font, NOT the raster one) to change page to 1251 possibly start CMD.EXE with the /U parameter You need to have SEPARATE batch file and Cyrillic text. Example copy and paste this in a Notepad or Wordpad and save as Unicode with name "choices.txt": Copy and paste the following in a Notepad or Wordpad and save as "plain" text with name "test.cmd" @ECHO OFF chcp 1251>nul more choices.txt for /F "tokens=1,2" %%A IN ('more choices.txt^|FIND "1"') DO ECHO %%B for /F "tokens=1,2" %%A IN ('more choices.txt^|FIND "2"') DO ECHO %%B for /F "tokens=1,2" %%A IN ('more choices.txt^|FIND "3"') DO ECHO %%B for /F "tokens=1,2" %%A IN ('more choices.txt^|FIND "4"') DO ECHO %%B chcp 437>nul Open a command prompt, make sure that you are using Lucida Console. Type in it: MORE choices.txt [ENTER] Now run test.cmd: TEST [ENTER] jaclaz

Have you actually READ the suggested "old" method? http://www.911cd.net/forums//index.php?showtopic=16713 jaclaz

You can tell that guy he could have a career at Seagate. jaclaz