Here is my 2 hours of work:
32-bit scandisk. What? No, no! Not really rewrited scan disk 9x function or such.

It's just a replacement over standard scandskw and:
- As a 32-bit application, it's more stable!
- As a 32-bit application, it can talk with other 32-bit extensions
- As a 32-bit application, it can be skinned!

It supports standard parameters:
scandskw.exe [disk list] [parameters]

/a Check all your local hard disks.
/n Start and quit ScanDisk automatically.
/p Prevent ScanDisk from correcting any errors it finds.
+additional+
/surface: Force surface scan
/custom: Disallow to change your settings
/noui: Background (no UI) scanning
/min: Minimized scanning

Tihiy

Tihiy:

AWESOME!

Replaced your Scandskw.exe with the old one (in C:\Windows\) and... works like a charm!
That was on my 'test bed' with 98seSP, 98se>ME, RP 3.5.

My 'base' (read 'base line') PC, with none of the above, crashed with:



No big deal. Just include it in the next release of the Revolution Pack (which I believe fixes the above problem).

Great (and lets not forget fast) work!

nitebat

AH FORGOT!!!
It works only with KERNEL32.DLL 4.10.2225 (included in SP2RC3 and higher)

Dear Tihiy

How do u do all such things can u send me what languages u know and how u improved u'r idea about modifying ms's all bugs etc.

please reply as good as u can so that all forum member can take advantage and improve there knowledge.

MSFN ENJOY!!!

Tihiy, downloaded & file size came out at 97.6KB[99,988 bytes] not 39.5k, is this right???

Scratch that, dld again came out 39.5k, don't know what hapnd first & second time???

Tihiy, thanks for this great work...

If you accept, I want to add it into the next version after some testing.

Original Win98 Scandisk wrapper is very small (4 KB). Why? Any idea? Also, what's the reason of Kernel32.dll-4.10.2225 dependecy? Just wonder...

Well, you can if it works OK. My scandisk is bigger, because
- Bit more features
- Includes more icon variations, including 32-bit ones
- PowerBasic compiler sux!
You can compress it with UPX executable packer.

As for Kernel32.dll, it's because it hard-coded function offset values - it's difficult to write proper calls for undocumented APIs.

PowerBasic?!

Yes, hahaha!
I'm writing everything on it.
That was my secret.

Gape,
I really hope you keep 3rd party applications as optional items that aren't installed by default, or provide a very easy to click checkbox to allow or disallow all 3rd party applications.

Some of us are purists that only want official MS bits installed on the PC. Some of us don't have a choice because we are in a work enviroment and installing 3rd party apps to replace 1st party apps is GREATLY frowned upon.

I've been trying to sell my coworkers on installing this across the company but it's been falling upon deaf ears for now. Obviously if 3rd party bits are installed by default it makes it 10x harder to convince an IT team to install this SP1.

I'm not asking you ot cater to me, I'm just asking for you to keep this SP as pure (1st party) as possible.

Rhelic,

Thank you for your comments. I'll try to make them optional.

Also I want to write again:
- SP will NOT be a collection of freeware programs.
- Only some replacements can be added to SP such as Scandisk, Format etc.
- Scandisk, Format and FDisk replacements are required for better HDD capacity support.

ahhh, i was going to post on this but see someone has beat me to it

if these are going to find there way into the SP might i suggest a new "large disk package" option.

Tihiy has not said that this scandisk addresses any of the concerning issues and imo alot of people will not have problems with the 137 GB limit as their existing partitions will be smaller than this. i 've made my views on unnecessary hacked file inclusion in the SP pretty clear previously and for much the same reasons as Rhelic. it seems much better suited (what with the skinning and added icons) to Tihiy's own ongoing projects.

anyway just my 2 cents...

miko:

tihiys' 32 bit ScanDisk is the result of disscusions we had concerning the LameSkin part of his Revolution Pack. I had asked if he could 'skin' no-standard buttons (like 'Start' & 'Close' in ScanDisk). He said it would be easier to write a 32 bit ScanDisk, which he did. It took him less then 2 hours.
Now, Scandiskw.exe is just a 'wrapper' for the 16 bit scandisk.exe in the C:\Windows\Command\ folder. The original Scandiskw.exe is a 16 bit app as well. Tihiy just wrote a 32 bit 'front end' for scandisk.exe. Defrag, on the other hand, is a 16 bit app with no 'dos' companion. So, unfortunatly, there will be no 'skinnable' version of defrag.exe anytime soon. So, miko, fear not, tihiy didn't re-write scandisk, just made a new (and nicer) GUI front end for it. It would be scary to introduce a new bug in such an important program as scandisk, but in this case that is simply impossible. Scandisk.exe remains untouched. Whether (or if) it ends up in Gapes' or Tihiys' packages is up to them. Wherever it ends up, I will and already am using it and I will pass it on to others... without fear.

Hope that clarifies things for you.

nitebat

WRONG! As before, it's wrapper over shell functions.
Delete scandisk.exe and check if you don't believe.

Thank you tihiy:

The functions had to come from somewhere. I had no idea they were buried so deep. Makes scense though. So now the 32 bit functions have a 32 bit 'front end'.

nitebat

Always willing to learn.

It is not a hacked file... However, I will make optional these tools.

We wrote that on various topics: 137 GB limit is a serious problem, it could not be fixed by smaller partitions.

Please read Petr's 137 GB post for details.

sorry, wasn't sure what it was,
but didn't mean bring up "hacked" things again,
i actually thought it was a 32bit rewrite of scandiskw
(maybe should have gone with "3rd party" like Rhelic said)
i will go read through all Petr's 137 GB post,
i've not really encountered this problem myself,
don't know why

sometimes i think you dudes get to serious too quick when someones just mumbling y'know, chill dudes

miko
(Also willing to learn)

folks:

A lesson learned I think. Tihiys 're-creation' of ScanDisk is nice looking (withe Lameskin) and adds some functionality. All using built in functions. What other system functions (hard to get at ones) can we write wrappers for. Tihiy suggested 'Network Properties' & 'Device Manager'. But what about extra Control Panel applets for things that don't have them (yet)? Adds functionality, puts things where folks expect it to be and, using 'system functions', there is little (ah... less) chance of introducing serious bugs.

Can a 'wrapper' be a '.cpl' file, tihiy?

nitebat

I can't see reason... Give me good example, please.

Tihiy,

Could you add an alert into this Scandisk utility for 137 GB problem ? If anyone tries to scan a 137+ GB disk, this tool should warn the user like that "the drive may be corrupt".

Without a problem!.. Anything more?

Nope!

Here it is:
Scandskw 32-bit replacement, v"1.1"
- Do not allows to check >128GB disk if it is not filled by data more than 128GB.
- Do not allows to check NTFS drives.
Resources can be translated.


Why i can't edit my post on 1st page?

They changed it so you can't edit some posts after a certain amount of time. Check the Site/Issues forum, I believe.

http://www.msfn.org/board/index.php?showtopic=47512

Thanks! But I don't understand that. Can you explain?

Click to view attachment
Well, if specified drive have size >128GB, this message will be shown.
If it does but it is filled to more than 128GB, this message won't be shown.

I'm not sure if it is a right method but it is one of.

I'm not sure about that.

Well, maybe I should remove that check.

Petr, rloew, and others: Could you make a comment?

^^ rloew recent post.
So, this check should be removed... or not removed... it is useless anyway.

If I understand correctly, scandskw should not be run on disks bigger than 136 GB.
The initial selection of disk to scan is done by this wrapper or by dskmaint.dll?
It would be good not to allow scan of bigger disk I think.

The best would be to allocate more memory so the scandisk could be able to work with bigger disks. Is there any chance for it?

Petr

I read all of the posts only to find out scandskw.exe does not apply to ntfs drive. thats what I've got!! Any suggestions on a scandisk prog that operates on ntfs??

Real good forum, tho