DOS experienced person req'd for 2 disk UJDA autopatcher

>NIL: · **Posted:** Wed May 07, 2003 2:53 pm

Task Title: 2 disk "dumbproof" version of the UJDA single disk version

Task Description: The current UJDA autopatcher boot floppy was supposed to be dumbprrof, but it has a major flow: The autopatcher and the flashing utilities are incompatible, and when you cannot run the flashing utility after you have ran the autopatcher without a reset.
This is pretty annoying, as you then have to compress your patched firmware file, save it to another floppy, reboot, extract the saved firmware and launch the flashing utility.

A LOT of people are complaining about that, and they don't have a clue how to get around in DOS mode... As I don't have the time to fix things in the current version of the autopatcher, as I will probably have to write it altogether, we need to provide UJDA user with a no brain 2 disk version that would do the job automatically.

Your job would be to pick up the 1 disk autopatcher version and make a 2 disk version out of it by inserting a reset command after the autopatcher command (mpatch) has been issued. The complete process ahs already been automated in the 1 disk version, it just needs to be adapted to fit a reset.

Technically, this is what the 2 disk step process would look like:

0/ User puts Disk 1 in drive and issues a reboots his machine
1/ Disk 1 boots, creates a RAM disk and extracts the needed tool in there (mpatch + compressor like pkzip or rar + reset command)
2/ Disk 1 runs mpatch and creates the patched firmware in the RAMDisk
3/ Disk 1 asks the user to insert Disk 2, compresses the created files (FLASH.BAT + the firmware + changes.log) and copies them onto floppy 2
4/ After a delay to make sure that all disk activity had ceased, Disk 1 issues a reset command (there are reset commands for DOS)
5/ Disk 2 boots, creates a RAM disk and extracts the needed tool in there (drvloadc + uncompressor)
5/ Disk 2 extracts the saved files to the RAMDisk and runs FLASH.BAT

Requirements:
- Proper DOS experience (you should know how to fiddle with DOS RAMDrives, AUTOEXEC's and such)
- Creativity (there might be a better way to do it... I wish PC's could use persistant RAMDisks between resets just like the Amiga did!)
- Owning an UJDA drive for testing would be a must

For more information on the UJDA autopatcher you can have a look at this thread or this post or pretty much of everything that is UJDA related in the Combo section

Tinstaafl · **Posted:** Thu May 08, 2003 5:43 pm

The following is my effort so far, in case it helps.

----------------------------------------
A little later.......

Just found the function to force a reboot from a website. Haven't tested it though.

ECHO G=FFFF:0000 ¦ DEBUG

Here's the page:http://www.robvanderwoude.com/debug.html#Reset

---------------------------------------

I've used a lot of calls to simple batch files to run each .EXE because I seem to recall that the CALL function returns to the DOS prompt on completion except when it's referring to another batch file. Once the child batch file completes the parent batch file continues its execution. Something like that, anyway...

Quote:

@ECHO OFF

REM This is a concept batch file. Purpose is to:
REM 1. run 'mpatch' to create an RPC1 patched firmware for the Matshita UJDAxxx series drives
REM 2. run 'pkzip' to compress the newly created mpatch files so they fit on a floppy
REM 3. copy the files to a floppy
REM 4. instruct the user to reboot using this floppy & choose the 'Write new firmware to DVD' option

EcHO =================================================================================
ECHO
ECHO Patching your Matshita DVD combo drive involves several steps:
ECHO
ECHO 1. Create the patched firmware & needed files.
ECHO
ECHO 2. Compress & then save the those files to another floppy disk
ECHO
ECHO 3. Switch off & restart your computer
ECHO
ECHO 4. Copy the needed files back to your PC
ECHO
ECHO 5. Write the new firmware to your DVD drive
ECHO
ECHO 6. Switch off & restart your computer again.
ECHO
ECHO This program will do most of the job but you'll be needed for a couple of tasks
ECHO
ECHO Every so often you will have to press a key to continue the job
EcHO =================================================================================

PAUSE

ECHO 1. Create the patched firmware & copy the needed files to floppy
ECHO 2. Get the patched firmware files from floppy & flash the DVD drive
ECHO 3. Exit this program ie Exit to DOS

ECHO This will automatically exit to DOS in 30 seconds

CHOICE /C:123 /N /T:3,30 Please choose a menu option

IF errorlevel == 3 goto EXITMENU
IF errorlevel == 2 goto WRITEDVD
IF errorlevel == 1 goto CREATEPATCH

:CREATEPATCH

rem use mpatch to create the patched firmware & copy the needed files to floppy

call z:\mpatch.bat -a

call z:\zipfw.bat
call z:\ziplog.bat
call z:\zippatch.bat
call z:\zipdload.bat

EcHO =================================================================================
ECHO
ECHO Label a blank, FORMATTED floppy disk 'DVD patch' & insert it in your floppy drive
ECHO
ECHO CAUTION! If the floppy disk is not blank then ALL files on it will be deleted!
ECHO
ECHO You will have to press a key once you've done this
EcHO =================================================================================

PAUSE

del a:\*.*
copy z:\patch.zip a:
copy z:\pkunzip a:

EcHO =================================================================================
ECHO
ECHO You must now insert the mpatch boot floppy ie the floppy you started with.
ECHO
EcHO =================================================================================

PAUSE

EcHO =================================================================================
ECHO
ECHO After exiting this program you must switch off & restart your PC
ECHO
ECHO before you can flash your DVD drive.
ECHO
ECHO Don't just use a 'soft' reboot using the 'CTRL-ALT-DEL' key combination.
EcHO
ECHO When you restart your PC choose Option 2: Flash the DVD drive
EChO
ECHO Remember to switch your PC off & then on again before flashing...
ECHO
EcHO =================================================================================

PAUSE

GOTO :EXITMENU

:WRITEDVD

EcHO =================================================================================
ECHO
ECHO Please insert the patch file floppy that was made in the last step
ECHO
ECHO You will have to press a key to continue
ECHO
EcHO =================================================================================

PAUSE

call a:\unzpatch.bat

EcHO =================================================================================
ECHO
ECHO Please make sure that there are NO(!!) power interuptions during this next stage
ECHO
ECHO WARNING!! If the PC is switched off while in the middle of writing the
ECHO
ECHO new firmware to your DVD drive you COULD ruin your drive!
EcHO
EcHO =================================================================================

call z:\patch.bat

GOTO :EXIT

:EXITMENU

EcHO =================================================================================
ECHO
ECHO Exiting now. Feel free to reboot or whatever...
ECHO
EcHO =================================================================================

EXIT

Called .BAT files:

zipfw.bat

Quote:

z:\pkzip -a z:\patch.zip z:\insert patch file name here

ziplog.bat

Quote:

z:\pkzip -a z:\patch.zip z:\insert .LOG filename here

zippatch.bat

Quote:

z:\pkzip -a z:\patch.zip z:\patch.bat

zipdload.bat

Quote:

z:\pkzip -a z:\patch.zip z:\drvloadc.exe

unzpatch.bat

Quote:

a:\pkunzip a:\patch.zip z:\

[/quote]

>NIL: · **Posted:** Sun May 11, 2003 1:57 am

Thanks Tinstaafl

I think there are a few other people working on this too so I think together, we should manage to get somewhere...

Tinstaafl · **Posted:** Mon May 12, 2003 1:28 am

Following up from before, & using that Debug reboot function, it should be possible to make a virtually user-input free method by calling sub-.bat files. That would avoid trying to time events or find out if they've complete d because the child .BAT would return control to the parent .BAT after it's finished.

I think the only input the user would have to do would be select from a menu after booting to either make the firmware or flash the drive.

Something along the lines of:

---------------
Boot & creat the RAM drive

Use 'Choice' to make the menu.

Offer 1st menu choice to create the RPC1 FW.

Call 'make firmware.bat' --> uses mpatch -a to makre the RPC1 FW.

Call 'zipfirmware.bat' --> uses pkzip to compress the new FW then returns control back to the main .BAT file
Call 'zippatch.bat' --> uses pkzip to add patch.bat to the archive, return control
etc etc until all needed files are added

copy the archive & PKUNZIP to a floppy

Instruct to put Disk 1 (the mpatch boot disk) back in the A: drive (saves a bit of disk space & stuffing around compared to making Disk 2 bootable.

Invoke Debug reboot function

Offer the 2nd menu choice to write the FW to the DVD:

Instruct to put Disk 2 in the A: drive
copy the archive + PKUNZIP to the ram drive

Call 'unzip.bat' --> runs pkunzip to unzip the archive
Give a warning re power etc during the write process
Call 'drvload.bat' --> the .bat created by mpatch.
Instruct them to remove the floppy disk
Invoke Debug reboot function (or maybe a instruct them to switch off & restart?)

--------------

Thoughts, anyone?

LaurentP · **Posted:** Fri May 23, 2003 6:23 pm

I HAVE BATCH FILES WHICH DO THE JOB !!!

they apply the scheme of NIL :
"
0/ User puts Disk 1 in drive and issues a reboots his machine
1/ Disk 1 boots, creates a RAM disk and extracts the needed tool in there (mpatch + compressor like pkzip or rar + reset command)
2/ Disk 1 runs mpatch and creates the patched firmware in the RAMDisk
3/ Disk 1 asks the user to insert Disk 2, compresses the created files (FLASH.BAT + the firmware + changes.log) and copies them onto floppy 2
4/ After a delay to make sure that all disk activity had ceased, Disk 1 issues a reset command (there are reset commands for DOS)
5/ Disk 2 boots, creates a RAM disk and extracts the needed tool in there (drvloadc + uncompressor)
5/ Disk 2 extracts the saved files to the RAMDisk and runs FLASH.BAT
"
and the idea of Tinstaafl for the reset.

I just patched my drive (UJDA 730 on thohiba 2410) with these files. The drive works fine and is now RPC-1.

Of course you still need to have a floppy drive...
You're welcome if you see any improvement. I already added some controls since the version I sent to Nil : maybe the patched firmware won't fit on the second disk, so if the batch can not create disk2, it displays an error message ant stops.

I didn't use any delay (see 4) above). It seems to me that drive A is not cached for writing and doesn't need any delay. Does anyone know about it ?

Now, who wants to try with his own drive ?

Tinstaafl · **Posted:** Fri May 23, 2003 10:18 pm

Well done! 8)

I've already flashed mine otherwise I'd give it a go. Are there exit options in the process? If so I might try it up to the point of writing to the drive to give it another machine trial.

LaurentP · **Posted:** Fri May 23, 2003 11:42 pm

Thanks for answering so quick.
You can test this way : make disk1, modify the autoexec.bat
"mpatch -a" -> "mpatch -q -a"
so mpatch doesn't try to patch your firmware (mpatch gives an error
if you try to patch an RPC-1 firmware)
reboot with disk1
it should create the second disk and reboot
then choose 2 in the menu (there is a menu for disk2 : 1=go on and flash, 2=abort flashing) and reboot windows.

There are 2 points I wonder about the batch :
- how big is the newdump.zip on disk2 (for me there was plenty of room left on the floppy) ; I don't know if any firmware version can fit.
Please post a message if there is a problem.
- is the automatic hardreset strong enough after flashing ? I had no problem between mpatch and flashing, but I didn't see the CD drive
when windows started for the first time, I had to restart it again (in fact, I'm not so sure and I would you like to know for others). That you can not test since your drive is RPC-1.

A precision for everybody : this patch is not dangerous for your drive (I mean no more, no less dangerous than mpatch alone). Either it works,
either it does nothing, and you will have to patch your drive manually.
So first try this patch !

Tinstaafl · **Posted:** Sat May 24, 2003 12:27 am

Thanks for that. I've only just started going through what you've written. I'm no hacker so it's slow going for me!

I think that's a good idea of yours to have a 2nd autoexec.bat pre-prepared for writing to the 2nd disk. I was thinking along the lines of "How the f... to make a single autoexec do both floppy 1 & 2 jobs...?". Also using pkzip to make a system disk. Forgot it could do that!

Re size of the FW: I flashed a colleague's 730 in a Toshiba 5100-603 (that's a UK spec machine) earlier in the week. The uncompressed FW was 1.0x Mb. I recall my 730's FW (in a Tosh. 5105-S901: A USA spec machine) was about the same size. Don't remember the exact size but AFAIK they were the same.

I doubt I would have been able to get his FW + needed files on the floppy without using PKZip. Size dropped to ~0.5 Mb for the FW, leaving plenty of room for the rest of the stuff. Bear in the 2nd floppy was without system files etc though. Didn't have that concern with my machine because I've set a FAT32 partition on it.

I'll do mine with your disk (tomorrow probably) & see what sort of space is used on a floppy in this sort of system and if there are any hiccups.

Guest · **Posted:** Sun May 25, 2003 7:27 pm

Hi again (to Tinstaafl),

Maybe you've seen the message from satria_wr at the UJDA 7xx autopatcher - v1.12 RELEASE forum. He's right but...
Nil is working on other firmwares and doesn't have much time. What can we do to help a bit ?
The problem with the installer was quite annoying and generated lost of posts. It's nearly resolved for the ones with a floppy. Still it needs to be tested. Then there is the problem to make a CD version.
It seems there a few people reading this post, the 'UJDA 7xx autopatcher - v1.12 RELEASE' would be better to have the new batch tested. I prefer to stabilize it before. I wait for your reply about the space remaining. Also if you've any idea about the patch, or about the 'echo' lines - english is not really my mother tongue. When the installer is OK, I will put it on the 'UJDA 7xx autopatcher - v1.12 RELEASE' forum.

At the moment, I try to make a version bootable from CD. If you want to help or anybody else (if anybody else is reading this forum ?). The problem with the CD is it is not possible to have 2 autoexec.bat files.
The second problem is to choose the drive.
The simple way to solves both problem is a rather long menu with :
"1) save on C - first step, mpatch"
"2) save on C - second step, flash"
"3) save on D - first step, mpatch"
"4) save on D - second step, flash"
"5) save on E - first step, mpatch"
"6) save on E - second step, flash"
"7) save on F - first step, mpatch"
"8) save on F - second step, flash"
"9) abort/manual"
People also need to use a FAT32 partition or access their NTFS partition from DOS. If you know something about NTFS (which is not my case), would you be able to make a quick help for NTFS ?

So anyway there is still some work before releasing the firmware for ujda.
But batch programming is from far easier than searching what is incompatible between mpatch and flash.

Tinstaafl · **Posted:** Sun May 25, 2003 8:31 pm

Since the goal is to make something that's useable by non-techie types I suppose adding some more information about what's happening would be nice. Not necessary, but reassuring to the person pressing the buttons. That's partly why I made use of so many ECHO lines in my (poor) attempt. I'll stick some in your work if you like.

re a bootable CD: What about combining the two autoexecs and using an

IF EXIST patch.bat GOTO 2NDBOOT

statement in the start of the autoexec.bat file along with a

:2NDBOOT

menu fork? After the first boot it could test for the existance of one of the about to be/newly created files such as 'patch.bat'. If it doesn't exist execution continues with the functions of your 1st autexec.bat including the reboot, and if it exists (because it's now the second boot) it skips to the the :2NDBOOT fork which would contain the functions of your 2nd autoexec.bat.

Not sure about how that would work with the environment strings but I guess that's not a major issue?

I've been tracking down some drivers that enables DOS to access NTFS file systems. So far I've found one that gives read only + another I think also allows write access. That would help solve the NFTS problems since it would allow the process to use the HD instead of a floppy. Of course, if we could use Linux we'd be fine since it has lots of support for the NTFS file system. Hmmm.....wonder if there are Linux versions of mpatch & drvloadc? Or even if they'd work using WINE...

Guest · **Posted:** Sun May 25, 2003 11:47 pm

Combining the two autoexec seems fair. I don't really see problems (what do you mean with environnement strings ? Is it the need for the user to choose the HDD letter ?).
If anybody patch twice with the same computer (is it realist ?), it's necessary to be sure to start the process from the beginning. If I use a single 'patch.bat', it has to be deleted at then end. It's cleaner to create and delete successive status files : s_begin_mpatch, s_mpatch_done, s_begin_flash, s_flash_done.

What would be nice is automatic scanning for a HDD. The only "maybe" problem is someone will patch a CD drive with a wrong firmware : if he does phase_1 with a drive, then changes drive, and launches again installer, drive 2 will be patched with drive 1 firmware . Seems quite impossible. Means an automatic scanning may work. Maybe I can try to do it with a DOS program (I kept an old Bordland compiler to make DOS program). But it is not a priority.

The problem with NTFS is (if I remember), moreover the problem of drivers, you can have sometime read and write access, or just read access or no rights. How is it possible to give write access ? Is it always possible ?
For Linux, the best is to ask Nil for mpatch. For drvloadc, ??? WINE is for Windows I guess, I think it cannot work because mpatch doesn't work under windows.
Anyway there exist NTFS drivers in DOS. And for Linux users, using a DOS installer is not a problem as soon as the installer is bootable.

About the 'echo' lines : I understand what you mean, updating process going on without giving any info... 'echo' is a good way to help because it is simple (a progress bar as does mpatch is a lot more work).
There's also a warning during the flash about the version, maybe it will better to inform about it and say no problem (with 'echo', just before ; a readme.txt is no good, because with DOS, you can not the read the .txt just when you need it). I will to try to find it again, a post speaks about it.
Anyway, if you see some 'echo' to add/change, welcome to them.

Tinstaafl · **Posted:** Mon May 26, 2003 12:31 am

I had thought the two autoexecs each set different parameters but now that I've looked at them again I think I was mistaken.

What about a couple of different downloads? One for use with a HD ie it assumes it's there & will use it, and the current one that uses the FD? Alternatively offer a menu for the user to choose to use their HD or not & then GOTO the relevent part of the autoexec.

Having the HD option would also allow floppy-less people to do their drive as long as their system can boot from the CD.

Not been able to test the floppy today. Trying to download some large files. Takes bloody forever without broadband.

LaurentP · **Posted:** Mon May 26, 2003 5:19 pm

So two news : one bad, one good

I read what I wrote yesterday. It was ambitious and a lot work (still NTFS exists with DOS, there's a free program - ported from Linux to DOS - which supports parts of DOS commands) . So I give up with it.

The good news : there is very simple way to make a correct reset at the end of mpatch.
I used the bootdisk.iso from NIL (installer CD version). Just after mpatch, I tried everything except rebooting. Then flash... and it worked !
In fact, for the CD version, a single command must be issued between mpatch and flash to correct the reset : dir %CDROM% !!! I don't know really why, I guess it resets something in the computer memory.
The floppy version from Nil + CD support + this command worked perfectly on my computer. Of course, it was mpatch -q -a not to patch twice, but this shouldn't change anyhting.
As soon as some cleaning is done, I send floppy and CD version on this forum.

>NIL: · **Posted:** Mon May 26, 2003 8:11 pm

LaurentP wrote:

The good news : there is very simple way to make a correct reset at the end of mpatch.
I used the bootdisk.iso from NIL (installer CD version). Just after mpatch, I tried everything except rebooting. Then flash... and it worked !
In fact, for the CD version, a single command must be issued between mpatch and flash to correct the reset : dir %CDROM% !!! I don't know really why, I guess it resets something in the computer memory.
The floppy version from Nil + CD support + this command worked perfectly on my computer. Of course, it was mpatch -q -a not to patch twice, but this shouldn't change anyhting.
As soon as some cleaning is done, I send floppy and CD version on this forum.

First of all my apologies for not replying to this topic any sooner (I was on holidays for some time). I am extremely grateful to all the people who contributed here, This is just great!

Now, I think LaurentP got a major breakthrough for all UJDA owners. If this is as easy as this, I think the 2 disk bootdisk version will be rendered obsolete, and we will see the end of something that has been plaguing us for way too long...

I'm just wondering: Do you need to have a CD in the drive for the dir command or not? I think some people reported that drvloadc would not work with a CD in the drive.

As soon as people confirm that your fixed version works, I will put it on my site as well. I think we still need to provide a dump option for people with a floppy drive, but I wouldn't go as far as trying to write on NTFS, as it seems too problematic.

Can other people with UJDA drive confirm that the dir command between mpatch and drvloadc fixes the damn freezout?

Guest · **Posted:** Mon May 26, 2003 8:50 pm

No you don't need to have a CD in the drive. Just it generates an error message "there's no drive, what do you want to do : abort, retry, failed" and the user must choose abort.

Here is the floppy version. For the user, it nearly looks like the v1.12 version of installer. The user can make a dump if he wants to. I transfered the echos about 'changes.log' to the end, so the user doesn't have to halt the batch.

LaurentP · **Posted:** Mon May 26, 2003 8:54 pm

Sorry, here is the floppy version.

LaurentP · **Posted:** Mon May 26, 2003 11:11 pm

So now I wanted to finish the CD version today, let's speak a little more.

Hello to Nil, hope you had nice holidays. The urgent in the message was not for you, it was for Tinstaafl to tell him he doesn't need any more to test the 2 disk version.
Also, Tinstaafl, you know it was a really good idea to publish your listing; I never took enough time to read the forum, when I saw this listing, I thought at least it must be a working version, just have to adapt the called .BAT files. In fact, in was not completely but once I was in the bath...

The CD version is below.
It is a modified version of Nil's boot_iso.zip.

>NIL: · **Posted:** Tue May 27, 2003 12:35 pm

Cool

I'll have a look at it as soon as I can. But obviously, what we need now are a handful of UJDA testers...

That error you get with no CD in drive might be a bit confusing for some users if we don't address it automatically. The ideal bootdisk would be one that patch the drive automatically.
I guess if you use the CD version of the bootdisk, you still have the disk in the drive when you issue the dir command so it's less problematic, but you might want to eject it before you run drvloadc (mpatch has no problem with a disk in the drive, as it's just a dump'n'patch tool).

Still I wonder what the dir command might be doing to reset the drive. I might try to investigate this if I can find the time.
I guess you need to have the DOS cdrom driver loaded as well as MSCDEX.EXE, right?

Guest · **Posted:** Tue May 27, 2003 12:57 pm

Have you looked into the PATH variable??

Windows 9X based boot disks appends to the path the CD-ROM drive.

LaurentP · **Posted:** Tue May 27, 2003 3:29 pm

Nil, it's funny you guess everything right. DOS cd drivers and MSCDEX come from your boot.iso.
I have found a way to avoid the error message : just launch MSCDEX not before MPATCH but after. The initialization of MSCDEX is sufficient, no more DIR.
I have updated the floppy version.

Is there everything to do the real installer ?

Also why does it works ?? That's all what I found :
A) The error text comes from MSCDEX, I just checked editing MSCDEX.EXE.
B) I have tried using IDEDIAG instead of MSCDEX, but this doesn't work (flash hangs). But idediag works correctly, so for me, it means the drive is correctly reset by mpatch.

C) When DRVLOADC works, it display
1) two title lines
2) the firmware version
3) these lines :
File and Drive is not the same model name
file model : UJDA 730 DVD/CDRW, drive model : UJDA 730 DVD/CDRW
continue (y/n) ?
If I say yes, the flashing goes on as normally.
I think I didn't have that the 1st time I patched my drive.
Maybe a bug and the message should be "same firmware. No need to flash".

When DRVLOADC hangs, it is just after the first two lines. Maybe DRVLOADC hangs when trying do retrieve the current firmware version or the drive model ?
Maybe it has to read current firmware and MPATCH should reset a position pointer before giving the hand ?

I know few about driver, but I would be interested by some explanation.

To Guest :
I don't know understand the post 'about the PATH variable'.
Anyway I tried to use a trick with PATH to avoid the No CD error :
add set the cdrom drive to PATH
then call a non existing .exe (like zyxw.exe). DOS scans all the drives to find the .exe. If there is no CD, this give exactly the same error as DIR.
That's logical, the error comes from MSCDEX, any DOS command will
trigger the same error.

Shilla · **Posted:** Wed May 28, 2003 12:02 am

Hi all,

Alot of the stuff that exists in the thread is wayyy over my head giving me a dumbfounded look on my face

But from the little that i know, you seem to be alittle stuck with the reboot command.

Have you considered 'restart.com' ? This file exists on the windows 9x cds, and im pretty sure it can be easily downloaded. Its compatibility is only with FAT / FAT16 / FAT32

On the NTFS side of things, maybe using the command 'shutdown -r' (shutdown and restart) and if you wanted to be user friendly 'shutdown -r -c "message" -t 10' (shutdown and restart; not before giving a message and a 10 second countdown)

I hope some of that helps

>NIL: · **Posted:** Wed May 28, 2003 1:33 am

LaurentP wrote:

I have found a way to avoid the error message : just launch MSCDEX not before MPATCH but after. The initialization of MSCDEX is sufficient, no more DIR.
I have updated the floppy version.

Even better!

Quote:

Is there everything to do the real installer ?

Don't think we need anything more. If the MSCDEX thingy fixes the freezout, then we have our dumbproof version at last.

Quote:

Also why does it works ??

I wish I knew. I've been using someone else's code for my ATPI/IDE DOS driver, and I suspect that somehow, either I'm doing something wrong when I relinquish the drive or the driver code is doing something wrong.
I've tried issuing various IDE/ATAPI reset commands at the end of mpatch, but none worked, so I'm a bit clueless.

But thanks to your great findings, this is no longer an issue. Phew!

Quote:

C) When DRVLOADC works, it display
1) two title lines
2) the firmware version
3) these lines :
File and Drive is not the same model name
file model : UJDA 730 DVD/CDRW, drive model : UJDA 730 DVD/CDRW
continue (y/n) ?
If I say yes, the flashing goes on as normally.
I think I didn't have that the 1st time I patched my drive.
Maybe a bug and the message should be "same firmware. No need to flash".

Could be. There are a few mixups in DRVLOADC.

Quote:

When DRVLOADC hangs, it is just after the first two lines. Maybe DRVLOADC hangs when trying do retrieve the current firmware version or the drive model ?
Maybe it has to read current firmware and MPATCH should reset a position pointer before giving the hand ?

Interesting guess... But to read the firmware, the software tells what address it wants to read, so it shouldn't be a reset.

I'd rather suspect that after mpatch exits, it leaves the drive in a bad state. And apparently, even if I issue a reset command from mpatch, the same thing happens, which leads me to think that the bug might not come from my code.

I'll try to create an autoextractible floppy image from your files tomorrow (huh, I mean today...) and put it on this site. Haven't checked the ISO, but if it's the same as the floppy, it should be absolutely fine (except I'd like to see you getting some credits for what you did

I'll update the readme anyway).

Once again (and I'll do it in French since I guess from your name that you do speak French) "Un grand MERCI! Tu viens de me retirer une sacre epine du pied!

"

And to all the Reloaded fans out there: No, I'm not swearing in French. Only daemons do that...

LaurentP · **Posted:** Wed May 28, 2003 10:41 pm

Stilla : the problem (slightly different from what restart does) is on the way to be solved, but thanks for the proposal and for reading the thread.

NIL:
I don't know what to answer. Thanks for your Merci

.
Appearing in some credits : if you propose, I can not (and wish not to) refuse. A credit line at the end of the readme would be great. But...please use Laoran and not Laurent. I would say it's a lot more personal.

Back a little bit to work : I join the files of the boot of the mscedx-after-mpatch CD version. They do all the work.

>NIL: · **Posted:** Thu May 29, 2003 1:48 am

No problemo

Just look at the popup message of the autoextractible from this thread...

I cleaned the floppy version from the drivers we don't need (SCSI, etc). The Oak one should suffice, since all these drives are IDE.

Once the floppy has been widely used, I'll upload the CD-ROM ISO.

At last, this half assed autopatcher of mine is turning into something that everybody should be able to use to free their drives...

slriv · **Posted:** Fri Jun 27, 2003 7:58 am

So is there anything I can do to help with this?

The Firmware Page

DOS experienced person req'd for 2 disk UJDA autopatcher

Who is online