[briton]

soporific, on May 12 2007, 07:31 AM, said:

briton, on Apr 22 2007, 05:12 AM, said:

The patcher decided my 48BITLBA was newer (there was a later version on the forum than the one included).

Yo Briton, can you tell me more about this ... which version of ESDI_506.PDR do you have installed?? (to find out, put a copy of the file you have installed into the \bin directory in the AP program directory, open up a DOS box at that location, and type GETVER ESDI_506.PDR and it will tell you the file version) ... i can't find any newer version of this update

OK. I did what you asked and it wouldn't help. So I researched and here is the short answer If you need more, let me know.

TINY answer: I used your GETVER on the new one (my one) and I get version 4.10.0.2226

VERY short answer: If your error check gives the existing file newer message when it discovers that the existing file is identical to the file AP will use to replace it, the problem is solved! (Sorry, I couldn't find where those file message reports are generated, but I am sure you know ) Basically, AP is finding that my file is the same date as the AP file even though the message says that the exisiting file is newer than the AP file.

SOMEWHAT LONGER answer with some details assumes that the message solution above is not the answer:

My version of ESDI_506.PDR is extracted from:
Enable4 8BitLBA | Break the 137Gb barrier!, Who said it couldn't be done? Enjoy your huge disks Post #1
Attached File(s)
[indent]4102226F.ZIP ( 14.1k ) Number of downloads: 1172
Manually inserted the extracted ESDI_506.PDR into the CAB file on the Win98SE disk before installation.

VERSIONS/DATES/SIZES GETVER gives version 4.10.0.2226. So I looked to see where your fix was coming from to compare. I found two files in the Hotfixes directory:

• 48bitlba.exe
  
• 48bitlb2.exe

which from the batchfile tells me are the two versions for normal and IBM laptops. I opened them and extracted the ESDI_506.PDR files to the bin directory and renamed them ESDI_506.LBA and ESDI_506.LB2 resepctively. Then using GETVER ESDI_506.* provides this result:

• 4.10.0.2226 Esdi_506.lb2 - AP file from 48bitlb2.exe
  
• 4.10.0.2225 Esdi_506.lba - AP file from 48bitlba.exe
  
• 4.10.0.2226 ESDI_506.PDR - extract from 4102226F.ZIP (the one I used)

Just to check that my version and the lb2 version match and the lba version doesn't in other respects, I checked file dates/sizes:

• Esdi_506.lb2 - Saturday, July 29, 2006, 02:02:18 - 28,526 bytes
  
• Esdi_506.lba - Thursday, July 20, 2006, 12:38:32 - 24,431 bytes
  
• ESDI_506.PDR - Saturday, July 29, 2006, 02:02:00 - 28,526 bytes

Same match/mismatch. Conclusion if the newer file message answer above is not correct? Although I am CERTAIN that I disabled the IBM laptop item and enabled only the normal enable48bitlba (after all, these were the default options weren't they? and I checked anyway!), AP is trying to use the laptop version anyway! I doubt this!

Hope this helps - let me know if you want more!

[Drugwash]

I doubt there's any way of checking if one's using/installing this on a laptop or desktop. Unless there's a CPU check... So maybe there should be an additional validation for mobile/desktop installation, which would then make the difference between 2225 and 2226. And if that would be done, then this should be a global check, so any other mobile/laptop upgrade within AP would take this setting into account.

[briton]

Yo soporific! Check this out and see if I am an id***! (If I am, I'll delete it cos it will be in the way!)

Extracts from HFSystem.bat follow:

 
:48BITLBA
:: ERRORLEVEL 194
:: this is the version for ALL PCs/portables EXCEPT IBM portables with removable disks
SET ABOOT=D
SET TRACK=48BITLBA
SET TITLE=Unofficial Update for Drives over 137gb (not for IBM portables)
SET FILES=48BITLBA.exe
SET CHECK=%windir%\SYSTEM\IOSUBSYS\ESDI_506.PDR
SET CHEC2=4.10.0.2225
SET USECH=FILC
SET USEDP=none
SET SKIP!=OP0901
%COMSPEC% /E:2048 /C "%LOC8%\code\MainCode.bat" DIALOG1

:48BITLB2
:: this is the version for IBM portables with removable disks
SET ABOOT=G
SET TRACK=48BITLB2
SET TITLE=Unofficial Update for Drives over 137gb (for IBM portables)
SET FILES=48BITLB2.exe
SET CHECK=%windir%\SYSTEM\IOSUBSYS\ESDI_506.PDR
SET CHEC2=4.10.0.2226
SET USECH=FILC
SET SKIP!=OP0902
%COMSPEC% /E:2048 /C "%LOC8%\code\MainCode.bat" DIALOG1
IF EXIST "%PATHZ%\@_DoBoot.tra" goto BootNow
IF EXIST "%PATHZ%\@_GoBoot.tra" goto BootNow
 

Shouldn't the 48BITLBA section SET CHEC2=4.10.0.2226 and the 48BITLB2 section SET CHEC2=4.10.0.2225 ? If you, you have the final digit of the version number wrong in each case. Just swap them and I can test it again (if I haven't changed that and tested myself lol)

Let me know!

[soporific]

briton, on May 14 2007, 07:06 AM, said:

Shouldn't the 48BITLBA section SET CHEC2=4.10.0.2226 and the 48BITLB2 section SET CHEC2=4.10.0.2225 ? If you, you have the final digit of the version number wrong in each case. Just swap them and I can test it again (if I haven't changed that and tested myself lol)

Hmmm, i dunno how you missed it ... maybe i've misread the situation, but in all your post text explaining more about which update is installed there's no mention of the determining factor about which update to install:

:48BITLBA
:: this is the version for ALL PCs/portables EXCEPT IBM portables with removable disks
SET CHEC2=4.10.0.2225

:48BITLB2
:: this is the version for IBM portables with removable disks
SET CHEC2=4.10.0.2226

Now, either you have an IBM laptop with a removable disk and as such should have installed the 4.10.0.2226 version, or you don't and thus should have 4.10.0.2225 installed. My guess is you've somehow missed this extremely important piece of info and have assumed that the latest file version is the one to install. Or you actually have a laptop and just have neglected to tell us...

I just re-read your posts and i think this is all to do with the fact you have inserted the wrong file into your CAB files. Unless you actually have an IBM laptop, you should have inserted 2225. This totally explains why AP is giving you the messages you are seeing. I dearly hope you aren't using that on a computer with hard disks over 137 gb! Stop using immediately!

And i did include a little bit of text that explained which one was which in the module options... i think you've had a Homer moment, my friend! D'OH!

about the sneak preview of v1.96: this is not in anyway an official release, a sneak preview in my language is a Beta where the code changes are finished but there still may be update additions to come. What i'm trying to say is there will be an actual v1.96 upgrade official release that you should download and install to replace the sneak preview version, so don't go and think you have v1.96 cuz you don't!

This post has been edited by soporific: 14 May 2007 - 03:04 AM

[briton]

soporific, on May 14 2007, 04:58 AM, said:

Hmmm, i dunno how you missed it ... maybe i've misread the situation...

OK. The reason I would have missed it is easy.

Years ago, I came to MSFN and checked out a thread which had started in which the idea of a Win98 Service Pack was being mooted. Not developed, mooted. So I went off and developed a purely Microsoft SP for my own uses with no other fixes that weren't available on the Update Site.

This year, I was pointed here by someone on another forum regarding the >137GB problem. I first read the thread in which its development was first mooted and then discussed (and argued especially with regard to a commercial version which already existed). That thread seems to have died when the final result was produced. When I understood THAT thread, I then went to the thread from which I could download the end result. I searched to see why the different versions/version numbers were not explained at the point of the download links. I then took the latest version and used it. It worked. I also compared it with the earlier version whose version number matched my Win98SE version number.

I posted a question on that thread asking which version number I should use (and should I match my Windows version number) as I hadn't found anything very clear. There hasn't been an answer. Maybe I should have reposted, but as the file was working, I didn't chase it. Then when I used auto-patcher, my Windows version number changed so I made the logical assumption that latest version was the one to use and only to revert to an earlier version if there was some reason not to.

Now it seems I was supposed to read some other thread (or this one?) to find out which file to download from the sticky post which held the download links.

So you are saying I should have been using the SECOND TO LAST download version? Hmmm! Wonder why my PC is alive considering my Win98SE partition is entirely above 137GB lol

Thanks for pointing it out. Any chance of someone doing something in that sticky post to point out which file to download for which use e.g. "this latest version is for IBM compatible laptops only and NOT for PCs"? I mean people who want that file don't necessarily read other threads!

Sorry to have reported incorrectly. Still very puzzled but thanks for the pointer!

[briton]

soporific there is something odd going on here.

My Win98SE version starts by installing KERNEL32.DLL version 4.10.0.2222 which is in the WIN98_31.CAB file on the CD and I copied to my windows\options\cabs folder from where I instal Win98SE.

ESDI_506.PDR comes from the same CAB file and was originally presumably the same version as the kernel. That is why I wasn't sure which Enable48bitLBA zipfile to download - the .2222 version zipfile or the latest.

Now according to the acquired wisdom from both this thread and that download thread I should be having startup problems because this is DEFINITELY not any kind of laptop - I ought to know, I built it lol

Now if I understand the (not very apparent) guidance on the other thread, one should ONLY download the 2226 version if your ESDI_506.PDR file has that version number - which the average mortal will only know if they find that their KERNEL32.DLL or Windows 98SE version number ends 2226.

Now come the problems. I manually replace the 2222 version of ESDI_506.PDR with the 2226 version and, luckily, have no problem with startup so I can finish the installation. Later on, I discover that Autopatcher is worth a try so I use it and include the 98->Me upgrade.

Now I find that sitting in my Windows\Options\Cabs directory is a KERNEL32.DLL version 4.10.0.2224 which I didn't put there and couldn't have come from my Win98SE CD. If that were being used, I should still NOT be using the 2226 version of the ESDI_506.DLL file. BUT in my Windows\System directory, the KERNEL32.DLL has version 4.10.0.2226. This of course means that in using the version 2226 version of ESDI_506.PDR, I am KIND OF following LLXX's advice (before she got banned) to use that version of the file .......

Question - how on earth did something somewhere decide to make my Windows 98SE version 4.10.0.2226 instead of 2224 ot 2222 and somewhere maybe even skipping 2225?

And if this is what happens when using the autopatcher and 98->Me, then the advice about IBM laptops is not correct but rather should use the Windows version number as identifier.

Any ideas what is going on here and what I should do? I am prepared to do a clean reinstallation, but I am not going to move the partition which means I need to replace the ESDI_506.PDR file during the windows installation. Presumably I should use 2225 for that even though the system will be 2222. And I can stop at each stage and check versions of kernel32.dll and esdi_506.pdr (the latter using getver.exe). If I need to test like that, should I disable 98->Me when I autopatch the first time so I can check the versions before and after?

Any thoughts!

[Drugwash]

The kernel version and the IDE driver version do not necessarily have to match.
The kernel may be (and most likely has been, through Auto-Patcher) patched/replaced by certain (un)official updates/upgrades, according to some versioning schema that follows MS' style, but that doesn't imply that any and all other files should be upgraded to the very same version number, if available.

In this case, the 2226 version of the pdr driver is clearly only for IBM laptops, so desktop users should stay away from it always.

Also, the official 2225 version of the pdr driver is coming from MS and is an upgraded/fixed version of 2222, meant to officially replace the latter. The patched 2225 version from LLXX is the very same official 2225, patched to support 48bit LBA. So it's safe to install LLXX' 2225 version over a 2222 pdr driver, on a desktop installation.

Someone please correct me if I'm wrong...

[soporific]

briton, on May 15 2007, 10:21 AM, said:

soporific there is something odd going on here.

I entirely agree with you, it sounds like crazy stuff ... !

briton, on May 15 2007, 10:21 AM, said:

And if this is what happens when using the autopatcher and 98->Me, then the advice about IBM laptops is not correct but rather should use the Windows version number as identifier.

OK, i think the warning to not use 2226 if you have a standard desktop is a theoretical warning - ie its possible something could go wrong, not that it will always go wrong. So just because you are using it without a meltdown of some sort doesn't mean its safe. I wish I knew more precisely but that is how i currently understand it. I remember people reporting that 2226 worked on their machines without a fuss.

briton, on May 15 2007, 10:21 AM, said:

Any ideas what is going on here and what I should do? I am prepared to do a clean reinstallation, but ...... Any thoughts!

Why go to the bother of re-installing if this is your only issue currently? It seems like you know how to boot into command prompt safe mode. Put the 2225 file somewhere easy ( eg c:\ ) and copy 2225 to %windir%\SYSTEM\IOSUBSYS\ eg c:\windows\system\iosubsys overwriting the 2222 file. All done. Am i missing something here?


OTHER NEWS

I have had a report of a problem in the Essential 3rd Party Apps module with the latest Flash update (i said i wouldn't include, i lied!) ... has anybody else downloaded the 1.96 preview and tried to run the above module? Did you by-pass Flash? If not, did you get the result below? Thanks in advance for any help tracking this down...

Quote

Now searching through the Essential 3rd Party Apps module...

ASET: Warning: syntax error!

*** program code error ***

Track: Flash4ie
Title: Flash 9.0.45 player & plugin for Internet Explorer
TvarB1: 9 0 45 0
TvarA1:
TvarB2: 9
TvarA2:
TvarR1:
TvarR2: ?

You are at the CantDetr label.
Please report this.

This update DOES use a new routine i dreamed up just recently ... it uses the registry to determine the program version. Lots of programs actually have a registry key that is used for advising on the program version --- Flash 9.0.45.0 installs a key called "FlashPlayerVersion" in HKCU\software\Macromedia\FlashPlayer and so the code simply uses that as the comparison version and the normal file version routine is then called to make the decision about whether Flash needs to be installed or not. The strategy is a bit iffy, especially if during a program's historical development a different method is used to store the program version - but it should work for Flash AFAIK ... so please report if you have seen something like the above ...

This post has been edited by soporific: 15 May 2007 - 02:54 AM

[charly]

OTHER NEWS

I have had a report of a problem in the Essential 3rd Party Apps module with the latest Flash update (i said i wouldn't include, i lied!) ... has anybody else downloaded the 1.96 preview and tried to run the above module? Did you by-pass Flash? If not, did you get the result below? Thanks in advance for any help tracking this down...

Quote

Now searching through the Essential 3rd Party Apps module...

ASET: Warning: syntax error!

*** program code error ***

Track: Flash4ie
Title: Flash 9.0.45 player & plugin for Internet Explorer
TvarB1: 9 0 45 0
TvarA1:
TvarB2: 9
TvarA2:
TvarR1:
TvarR2: ?

You are at the CantDetr label.
Please report this.

Yes--got the same thing--charlie

[briton]

OK thanks very much Drugwash and soporific. You both made it very clear.

I knew the warning about the IBM laptop version was theoretical - as in "it MAY cause problems".

However, there is still a problem with the way in which the files are provided. The Enable48BitLBA Download Thread simply states:

2006-07-29 20:05 Win98SE version (4.10.2226) released - only for replacing an existing v4.10.2226 file

As that is a sticky post and the thread is only sporadically posted to, this means that there will be users like me who, finding they have version 4.10.2226 will get stuck wondering. Many of them will NOT know how to find out the version of the .pdr file but WILL know how to find their version number.

Can't change the sticky. Not much point burying the advice in a quiet thread. My point is that it would probably be a good idea for a Moderator to amend LLXX's sticky post to explain that the 2226 version should ONLY be used if the PDR file has that version number regardless of what the kernel/windows version is and maybe a pointer to how to use GETVER to find out (I notice that GETVERS doesn't work either). Remember that LLXX cannot amend that post for obvious reasons so could someone else please? (You might also want to make it more obvious which files to download - like put the type of windows against the file link - the number of downloads suggests that many like me downloaded 2226 thinking it was simply the latest version - in fact EVERYONE seems now to be downloading that version and I doubt there are that many IBM laptops around lol)

For me, that's it - I am back on track thanks!

This post has been edited by briton: 15 May 2007 - 09:57 AM

[thmck]

QUOTE
Now searching through the Essential 3rd Party Apps module...

ASET: Warning: syntax error!

*** program code error ***

Track: Flash4ie
Title: Flash 9.0.45 player & plugin for Internet Explorer
TvarB1: 9 0 45 0
TvarA1:
TvarB2: 9
TvarA2:
TvarR1:
TvarR2: ?

You are at the CantDetr label.
Please report this.




I got the same error, everything else was good.

[soporific]

<text snipped>

does the Flash update work for anybody at all or is it just me?

This post has been edited by soporific: 16 May 2007 - 06:03 AM

[Drugwash]

I got a better idea, if you don't mind... Here's the install log for Flash 9: link. Check the registry keys...

Oh, forgot to mention: this is from a manual install, not from Auto-Patcher.

This post has been edited by Drugwash: 16 May 2007 - 06:00 AM

[soporific]

Drugwash, on May 16 2007, 09:57 PM, said:

I got a better idea, if you don't mind... Here's the install log for Flash 9: link. Check the registry keys...

Oh, forgot to mention: this is from a manual install, not from Auto-Patcher.

thanks man, i was looking at the wrong key, and in the wrong place. Cheers.

Please find attached the fix for the flash problem.

and due to some information from this post, the official version of 1.96 is going to be a bit different.

Attached File(s)

•  flash_fix.zip (13.38K)
  Number of downloads: 12

This post has been edited by soporific: 16 May 2007 - 06:29 AM

[soporific]

feed me back... v1.96 ... is it ... is it not ... only a short post away ... go to it!

[Kelsenellenelvian]

I keep having probs with nod32 and a coupla files.

I will disable it in the morning and try again.

[soporific]

Auto-Patcher for Windows 98 SE (English)

(hopefully the) very last preview is now available, get it here:
upgrade 1.95 PR2 to 1.96.50
16.7MB

If nothing is wrong with this release, it will simply be re-branded to Auto-Patcher for Windows 98se May 2007 and released as full & lite versions. The full version will also include Net Framework 1.1. So if there are no major bugs reported, you can think of this as the proper release described above. The only thing is you will have some obsolete files inside the program directory - so if you don't have access to broadband, just stick with 1.95 PR2 and this upgrade to 1.96.

This post has been edited by soporific: 20 May 2007 - 09:10 AM

[Mazabuka]

soporific, on Apr 3 2007, 05:23 AM, said:

Mazabuka, on Apr 3 2007, 02:42 AM, said:

Quote

2) Turn debugging on. In the Start Menu shortcut folder that is created when you install Auto-Patcher (AP) there is an icon that will turn it on for you. This will greatly help tell us WHERE the problem occurred. Start the report process as normal, then when it terminates, look for the DEBUG.TXT file this is created in the logs directory and post that to this thread.

I tried this - the results were exactly the same as above in point 1) meaning that the file REPORT.TXT was created instead of DEBUG.TXT?

No, both files are created when you turn debugging on. Can you not find DEBUG.TXT when you use debugging? This may still help us although i think the problem lies with your system rather than the program (although I plan to include any code that will fix this problem).

Mazabuka, on Apr 3 2007, 02:42 AM, said:

he problem I have seems to be related to the amount of environment space I have configured on SE.

Are you saying you have specifically configured your OS to use a certain amount of environment space (ES)? Or are you reporting the default ES that Windows allocates... You are correct when you say that it doesn't make sense that you are having ES problems because I DO set the amount of space that I think is required to run the module. You can try adjusting these to see if it helps -- sorry, i didn't create a variable for this so you'll have to do them all manually.

Quote

Having got the reporting system to work successfully, I then proceeded to install the fixes in the Stability Module. Phase I of the installation appeared to proceed without any problems. However, when phase II of the installation started after the reboot, two error different error messages were displayed, viz.:

i) "out of environment space"

ii) "- the above title started to loop thru installations and so was not installed again"

The second error message is very likely related to the first one. When you start getting ES messages, this means that variables aren't being set properly and any code that uses the variables not being set will crash. Yep, i'm very sure about this one.

Mazabuka, on Apr 3 2007, 02:42 AM, said:

Whilst I understood the first error message, the second one was too cryptic for me to comprehend.

It means that the hotfix is trying to install for the second time when it should only need to install once.

Mazabuka, on Apr 3 2007, 02:42 AM, said:

As a consequence of receiving the two error messages, I was concerned that the some of the fixes in the Stability Module may not have been installed correctly, or not at all. I thus manually checked that each fix had been installed correctly, which to my surprise was the case.

This makes perfect sense to me. The module installed properly, its just that when you rebooted, the ES problem returned.

I will check out those Strings you suggested ... I will also reply again when i've done some investigating ...

Soporific. I've Upgraded from AP 1.95 PR2 to 1.96.50 - the bad news is that the problem still persists in AP 1.96.50. In addition, debugging cannot be turned on from the shortcut folder in the Start Menu.

The good news is that there appears to be a very simple workaround to the problem of insufficient environment space that I am experiencing.

Once I realised that using AP to patch a vanilla SE system that has no applications installed on it is very different to using AP to patch a SE system that has several applications installed on it, a workaround to the problem became readily apparent.

In brief, all that was necessary was for me to "configure" my SE system in such a way as to make it appear to AP that it is a vanilla system without any applications installed on it. There are two ways to do this:

1) Boot SE into Safe Mode and then run AP
2) Use Msconfig to change SE's bootup configuration from "Normal startup - load all device drivers and software" to "Selective startup" in which the "Config.sys", "Autoexec.bat" and "Load startup group items" options are disabled, followed by a reboot and then running AP.

I've tested AP's reporting system (including the debugging option which I ran from AP's install folder) using both methods without experiencing any problems.

Once you release the full version of AP 1.96.50, I will download it and test AP further by installing some of the other patches that remain to be installed on my SE system. I would not expect any further problems related to environment space when I install the patches, provided I use the Msconfig workaround and reboot prior to using AP to install the patches.

I think the new AP user interface is a big improvement on the previous one, and the addition of the "Help" system also gets a big thumbs up!

This post has been edited by Mazabuka: 25 May 2007 - 01:37 PM

[soporific]

Mazabuka, on May 26 2007, 03:53 AM, said:

I will check out those Strings you suggested ... I will also reply again when i've done some investigating ...

Fair enough, i'll re-investigate.

Everyone: for the latest news, please see the first post.

RE: those having problems even getting AP to run under normal conditions...

i'm going to improve the environment space functioning by adding a test at the very start that will warn about systems that don't provide enough for the program to work properly. It's not good enough (it seems) to wait for users to see 'Out of environment space' (OES) warnings - i suspect that the messages aren't always appearing when OES is the problem. So the code will at least rule this out. I will release a new version of Autopach.bat based upon the 1.96.50 upgrade that was released.

This post has been edited by soporific: 26 May 2007 - 12:24 AM

[soporific]

OK, v1.96.51 is out now!! ...... don't get too excited, all this is for is for people who are experiencing problems with Auto-Patcher even starting. Everyone can install it, but you won't notice much if everything is OK. I have included a newer version of START_DEBUG.bat but that was only because i forgot to update it for the earlier release. Doh. The release is an installer that does all the work for you, just run it and choose the install directory for AP.

WHAT is in the update?

The change is that the very first thing the program does after locating the program directory and running AutoPach.bat, is an environment space test to check that enough space is available and that all the code-checking variables will be able to be set properly. I'm not actually that confident that this addition to the program is going to solve most problems, but its good to have in there to rule out the possibility.

Technically speaking, lots of text is assigned to each of the module choice variables, which mimics what the program is going to do but is designed to catch any errors (unlike the previous method which was a "wait for error to appear and not handle it at all" method). It is possible to trip the space warning and for it to be a false alarm but i've coded for this situation so its still fine to use.

grab it here:
http://soporific.dsleague.com/downloads/Au...6.51_update.exe
file size: 226kb

you MUST have v1.96.50 already installed.

This post has been edited by soporific: 26 May 2007 - 12:18 PM